I am trying to replicate my virtualbox-based development environment in the cloud.
I have 3 VMs running
- A server with a SQL Server instance that also hosts a shared drive
- A web server running IIS 7 with the directories containing the website shared for easy publication
- A development machine where I develop and test two solutions, one that builds to a website and another that builds to a windows forms app, both of which access the SQL server. I have also installed SQL Server Management Studio (SSMS) on this machine.
I have created the virtual machines and I am trying to get them to network properly. Unfortunately, no matter what I do I have been unable to get the network to identify as private. Each of the VMs sits there with the connection flagged as "Identifying..." and the network defaults to public settings. I have created Windows Server 2008 R2 and Server 2012 images and they all have this issue.
When the machines are in this state I have internet access, but the machines do not show up in Explorer or when I use SSMS to browse for SQL instances.
I am creating the VMs isolated in their own cloud service. Each of them is within the same subnet of a Virtual Network, and I have installed a DNS server on one of the servers and pointed the Virtual Network at it.
I can successfully ping the machines by name (I created an inbound rule on each machine's firewall to let ping through), and nslookup uses my DNS server to successfully resolve names. i can even access network resources by name once I configure the public network profile appropriately.
However, I am at a loss as to why the network is stuck at Identifying...
Does anyone have any ideas?