I have VMs configured to use either an Internal virtual switch or a Private virtual switch
As neither an Internal or Private virtual switch are bound to a physical NIC they have no way of getting internet connectivity. This for me is a real problem as I want to connect to the internet to download updates and other files from these VMs.
I’ve tested this solution on Hyper-V running on Windows Server 2008 R2 Enterprise, 2012 R2 Standard and Windows 10 Professional. This solution assumes the following:
- You have already created a standard Private and/or Internal virtual switch
- You have a physical NIC on the Hyper-V host that is already connected to a network that has Internet access.
Step 1: Open the services on the Hyper-V host and select the “Routing and Remote Access” service, enable it and set it to automatically run.
Check also that the “Internet Connection Sharing (ICS)” is set to automatic and is started.
Step 2: Open the Network and Sharing Center (NCS) and open the properties of the physical NIC on the Hyper-V host that is connected a network that has Internet connectivity. Select the Share tab and enable the “Allow other network users to connect through this computer’s Internet connection” option.
In the drop down menu select the virtual switch Private/Internal NIC which will use this ICS connection. In the NCS a new icon will appear called “Incoming Connections“.
Step 3: Staying in the Network and Sharing Center open the properties of the virtual switch Private/Internal NIC and ensure it has a static IP address. In my tests it was automatically assigned 192.168.137.1/24, but you can assign any address as you require – make a note of this as it is needed in Step 4.
Step 4: For the VMs to use this ICS, login to them and open their Network and Sharing Center and configure the NIC to have a static IP address in the same subnet. In my example I gave my VM the address 192.168.137.10/24. Finally set the default gateway for the VM to be the IP address of the address of the virtual switch Private/Internal NIC, in my case 192.168.137.1.
In my example I also added the google DNS server 220.127.116.11 to the DNS settings in the VM, but configure this as fits your requirements.
Step 5: Test you have Internet connectivity. In my example no further configuration was required, I had Internet access immediately
Important: As this client has got direct Internet access it is advisable to install an anti-virus solution and ensure it is fully patched.
Disclaimer: provided “AS IS” with no warranties and confer no rights