New
#11
That did not work.
Hyper-v virtual switch breaks my network
-
-
-
New #13
External switch still does work, but I don't want to use it as it causes problems elsewhere.
-
New #14
The thing with default switch is that it can't be deleted and recreated. Only way to do it is completely remove Hyper-V feature, restart and enable Hyper-V again.
You could try setting static IP and DNS for network adapter on guest using default switch. Set IPv4 default gateway to 172.21.183.161 and IPv4 address to 172.21.183.XXX where XXX is a value between 162 and 255. Subnet mask needs to be 255.255.255.240.
Sample NIC settings from a VM using default switch:
Same from a Finnish Hyper-V guest:
Please post back telling if it works or not.
-
New #15
Static DNS didn't work. Then I disabled Hyper-V, restarted and enabled it again. That made the default switch work and now my VM has internet access.
Thanks for your help.
-
-
-
New #18
The default switch is somewhat problematic, I simply cannot understand why MS has decided that it can't be deleted and re-created, to resolve connection issues or simply because user does not need it.
Sometimes it simply does not work and as no apparent reason can be found, the only option user has left with is to disable Hyper-V feature, restart and enable Hyper-V again. This can in some cases lead to lost virtual machines.
That being said, I find it positive that there now exists an option to set up a VM using NAT networking. Default switch is an important feature, I just wish it could be managed as any other switch.
BTW, a workaround for those users who'd prefer not to create an external switch but also would prefer allowing full and easy networking between host and guest thus not wanting to use default switch is simply to set up an internal switch in Hyper-V Virtual Switch Manager, make VM to use it, and share host's Internet connection with this internal switch.
Kari
-
-
New #19
I'm experiencing a similar, frustrating issue w/the new "Default Switch" in Hyper-V on Windows 10 1709. My machine is a clean install of Windows 10 Enterprise (1709). For me, this didn't start happening until 1709 -- prior to the clean install, I was using build 1607 so I went straight to 1709 (no 1703 in the middle)... This is my first go-around with the Default Switch. Here's what happens with me... pretty much every day, I launch any VM and get the dead network icon (like above -- no network connection in the guest)... the only way for me to get it back is to reboot the host computer. I tried just restarting Hyper-V but that did not work. This seems really ill-conceived... why would I have to reboot my computer every day to make Hyper-V networking work? It's frickin' ridiculous. I hope that someone reports this bug to MS and they come out with a fix in one of their cumulative updates.
-
New #20
I'm in the same boat with the Default Switch. Like CrisAtFCPS, this is a clean install (not an upgrade) of 1709 (Fall Creators Update). The Default Switch was set to internal and completely cut off from the network. For me, the "fix" (really just a workaround, but easy and 100% effective) was to add a new manual switch, bind it to the correct NIC (the host has 2 that are active), and then remove the Default Switch NIC from the client. This forces the VM to use the correct switch and doesn't change with reboots of host or client. Simple and effective, but frustrating that this is needed for each client. If I could have just modified or Removed the Default Switch, this would prevent the problem on all future clients permanently.
Quote
Related Discussions
