Sounds like you need a router to serve as the gateway; if you're behind a NAT interface, then, you'll need something to get you onto the internet. You'l have to use RAS as a router only to do that. I've not looked at this in a long time, but that's the basic principle. -----Original Message----- From: Zameer Mahomed <core7xx@gmail.com> Sent: Sunday, February 10, 2019 8:00 AM To: 'Blind sysadmins list' <blind-sysadmins@lists.hodgsonfamily.org> Subject: [Blind-sysadmins] Hyper-v: Internet on an internal switch? Hi Listers, for those of you using Hyper-V, My scenario is that I would like to have an internal switch but have this switch connected to the Internet. I understand this is possible via NAT. I am currently using Windows 10 enterprise, build 1803. Using powershell, I have done the following: New-VMSwitch -SwitchName Internal -SwitchType Internal the interface index of the switch I just created is 33. New-NetIPAddress -IPAddress 10.10.4.1 -PrefixLength 22 -InterfaceIndex 33 New-NetNat -Name External -InternalIPInterfaceAddressPrefix 10.10.4.0/22 I've gone in to the settings of a VM under network adapter, and selected the name of the switch I created earlier. I've also assigned the vm a static IP address and used 10.10.4.1 which I created earlier for the gateway. However, I am still unable to access the Internet. I am able to access other vm's and the host. Your help would be much appreciated please? Kind Regards Kind Regards _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org