I am having some issues with the configuration of my Hybrid demo environment. I have the following configured:
Laptop
- Hyper-V VM - AD01 (External Adapter - 192.x.x.x, Public Internal Adapter - 10.0.x.x)
- Hyper-V VM - SQL01 (External Adapter - 192.x.x.x, Public Internal Adapter - 10.0.x.x)
- Hyper-V VM - SQL02 (External Adapter - 192.x.x.x, Public Internal Adapter - 10.0.x.x)
- Local domain Configured. SQL01 & SQL02 added to the Domain
- WSFC configured with SQL01 & SQL02
Azure
- VNet Configure - with Point-To-Site VPN
- Connection Address Space 10.0.x.x/24
- VNet Subnets (subnet-1 10.0.1.x, Gateway - 10.0.1.x)
- VM -ASQL1 (10.0.1.x)
All 3 hyper-v VM's on my laptop have the P2S configured and connected. The dashboard for the Vnet shows 3 clients and 1 Azure VM. Given every time the P2S will be connected the PPP Adapter receives a new IP Address. Once I have connected the P2S VPN, I run an IPConfig /all to receive the IP Address of the PPP Adapter. I take that Address and set it to the preferred DNS address on the ASQL1 IPv4 address.
The Azure VM (ASQL1) has been joined to the Hyper-V Domain. I am able to ping AD01 and it returns the PPP Adapter Address of the AD01 server. If I ping the SQL01 or SQL02 VM's I initially receive the correct IP address for those VM's but then proceed to receive a time out.
I am assuming I am missing something in my setup to enable the comms from the Azure VM's to talk back to the Hyper-V VMs. Is there something I need to configure on the AD01 server?
All VM's both Hyper-V and Azure are running W2k12R2 and all firewalls are turned off. The AD01 server has only been configured with the AD Domain Services Role and the DNS Server Role along with the RAS Connection manager Feature.
Thanks
Warwick Rudd (MCM - SQL 2008 | MCT)
(SQL Masters Consulting |
My SQL Server Blog | Twitter)