Windows 10: Providing Hyper-V VMs with network through custom NAT in Windows 10

I'm trying to set up a NAT on Windows 10 to provide Hyper-V VMs with access to both Internet and Cisco AnyConnect VPN configured on the host machine. In accordance with this manual I executed the following PowerShell script:New-VMSwitch -SwitchName 'VM NAT switch' -SwitchType InternalNew-NetIPAddress -IPAddress '192.168.2.1' -PrefixLength 24 -InterfaceAlias 'vEthernet VM NAT switch'New-NetNat -Name 'VM NAT' -InternalIPInterfaceAddressPrefix '192.168.2.0/24'The script was successfully completed and VM NAT Switch was assigned to a VM. But the IP address the VM was provided with at startup wa

:)

 

Windows 10 Hyper-V "Default Switch" question

Hi,

The VMs on Windows 10 Hyper-V set to use the default switch on Windows 10 Hyper-V receive dynamic IP addresses. There is no setting to set it to static. I'm assuming there is NAT set up behind the scene that
supplies those IPs.

To get around this issue I have set up a NAT and everything works but came across a Hyper-V on Windows 2016 article that stated that on Windows only a single NAT is supported. Two questions:

1- Is is still the case on Windows 10?

2- When I do issue "Get-NetNat" command, only my custom NAT shows up. I don't see the one which I assumed to be behind the "default switch" shows up. What am I missing? Or is my assumption incorrect?

Thanks!

 

Hyper-V networking

Windows 10 Pro, Build 10586.71. Hyper-V installed. All was working well, and then I got a chipset update from Dell. Installed the update and rebooted computer. After that networking was not working correctly, windows showed limited connectivity. I looked
a little to roll back the driver update, but Windows did not show a new Nic card driver and the chipsets I looked at also did not show a current date. The Dell Command update program does not provide a way to uninstall updates.

I tried to access hyper-v switch manager but it returns an error that "an error occurred while trying to retrieve a list of virtual switches". Also tried using the powershell cmdlet but got a general error.

I accessed the networking center and deleted the Hyper V adapter, then edited my LAN card's config disabling the two Hyper V protocols and enabling the rest. This let me get back on-line with my computer. I have tried uninstalling the Hyper V feature,
reboot, reinstall - but I am still unable to access the switch manager. I then removed the feature again, re-named the C:\ProgramData\Microsoft\Windows\Hyper-V directory, rebooted, added the feature again. This time (obviously) none of my VM's show up but
I'm still unable to access the switch manager.

There is no critical data in my Hyper V, I use it for testing, re-creating issues, learning, etc. Is there a way for Windows 10 (or something designed for server 2012 that will apply) that I can use to fully reset the Hyper v networking, or fully rest all
of hyper v so I can get it working again? I do use the workstation heavily, it's my work computer so it would be very difficult to impossible to reinstall the OS.

Thoughts and suggestions appreciated.

 

Hyper-V NAT (finally)!


It looks like you can use Powershell to configure a NAT adapter in Hyper-V:
Hyper-V Virtual Switch using NAT Configuration | Thomas Maurer