Cannot connect to network in Hyper-V when using default network

Page 1 of 2 12 LastLast

  1. Posts : 15,441
    Windows10
       #1

    Cannot connect to network in Hyper-V when using default network


    I have a Hyper-V VM which refuses to connect to internet when using the default network switch, but connects fine if I use an external switch.

    Unfortunately, there is something screwy in Windows 10 since 1803 as my broadband download speeds nosedives when using an external virtual switch.

    If I use the default switch, my broadband download is fine.

    I tried using trouble shooting and network reset but they fall over with no IP address assigned.

    Any ideas?
      My Computer


  2. Posts : 16,623
    Windows 11 Pro X64
       #2

    I think the default would be best for a local network, but you need the External to connect to the internet. Are you using DHCP, maybe a static IP would help, I believe the behavior of the default switch goes to public when trying to access the internet, and will not let you change it to access the internet.

    For network reset, did you use the built in W10 in settings, or CMD prompt netcfg -d?

    I believe Kari said the Ext switch is needed for internet access.
      My Computers


  3. Posts : 17,661
    Windows 10 Pro
       #3

    Dude said:
    I believe Kari said the Ext switch is needed for internet access.
    @Dude, a minor misunderstanding, most probably caused by me.

    Default switch, although it's type is Internal, is capable to connect to Internet. For instance, at the moment it is the only switch I have, having deployed a new custom image on my host and not set it up completely yet:

    Cannot connect to network in Hyper-V when using default network-image.png

    My virtual machines have no issues in connecting to Internet using it:

    Cannot connect to network in Hyper-V when using default network-image.png

    What I have said is that because Default switch puts VM behind NAT, the networking with host is if not impossible but at least extremely difficult. You can map shares from host using host name (not IP) but host will not be seen on VM's Explorer > Network because it is on different subnet.

    @cereberus, I read your post as soon as you posted it, having done some extensive Googling and Binging, trying to find a fix. Unfortunately, at the moment, I have found nothing.

    If your other VMs can connect using Default switch, you could try if this works. Check IP, DNS and DHCP settings of virtual NIC on a VM where Default switch is working, and use those values to setup the problem VM to use static IP, DHCP and DNS. Screenshot from VM shown in previous screenshot:

    Cannot connect to network in Hyper-V when using default network-image.png


    Kari
      My Computer


  4. Posts : 15,441
    Windows10
    Thread Starter
       #4

    Kari said:
    @Dude, a minor misunderstanding, most probably caused by me.

    Default switch, although it's type is Internal, is capable to connect to Internet. For instance, at the moment it is the only switch I have, having deployed a new custom image on my host and not set it up completely yet:

    Cannot connect to network in Hyper-V when using default network-image.png

    My virtual machines have no issues in connecting to Internet using it:

    Cannot connect to network in Hyper-V when using default network-image.png

    What I have said is that because Default switch puts VM behind NAT, the networking with host is if not impossible but at least extremely difficult. You can map shares from host using host name (not IP) but host will not be seen on VM's Explorer > Network because it is on different subnet.

    @cereberus, I read your post as soon as you posted it, having done some extensive Googling and Binging, trying to find a fix. Unfortunately, at the moment, I have found nothing.

    If your other VMs can connect using Default switch, you could try if this works. Check IP, DNS and DHCP settings of virtual NIC on a VM where Default switch is working, and use those values to setup the problem VM to use static IP, DHCP and DNS. Screenshot from VM shown in previous screenshot:

    Cannot connect to network in Hyper-V when using default network-image.png


    Kari
    Thanks @Kari, that was what I was going to try next. I would not bother and just use an external switch if it was not for the Hyper-V network adaptor bug that affects some users - it kills my host download speeds but bizarrely not my upload speeds.
      My Computer


  5. Posts : 17,661
    Windows 10 Pro
       #5

    cereberus said:
    Thanks @Kari, that was what I was going to try next. I would not bother and just use an external switch if it was not for the Hyper-V network adaptor bug that affects some users - it kills my host download speeds but bizarrely not my upload speeds.
    I have the same issue. As soon as I create an external switch, my download and network transfer speeds drop dramatically. Not having any external switches, only using Default, this won't happen.

    Kari
      My Computer


  6. Posts : 15,441
    Windows10
    Thread Starter
       #6

    Kari said:
    I have the same issue. As soon as I create an external switch, my download and network transfer speeds drop dramatically. Not having any external switches, only using Default, this won't happen.

    Kari
    This bug is really irritating as you cannot RDP from a remote pc direct to VM using the default switch as far as I can tell. I have to RDP to host and access it via host.
      My Computer


  7. Posts : 17,661
    Windows 10 Pro
       #7

    cereberus said:
    This bug is really irritating as you cannot RDP from a remote pc direct to VM using the default switch as far as I can tell. I have to RDP to host and access it via host.
    Instead of using RDP to connect to virtual machines which are using Default switch on remote host, I just add that host to my Hyper-V Manager on primary host.

    Click Hyper-V Manager on left pane:

    Cannot connect to network in Hyper-V when using default network-image.png

    On Actions pane, select Connect to Server:

    Cannot connect to network in Hyper-V when using default network-image.png

    Enter remote Hyper-V host name:

    Cannot connect to network in Hyper-V when using default network-image.png

    If that remote host does not have exactly the same admin user credentials than your primary host, select Connect as another user entering the credentials to remote host:

    Cannot connect to network in Hyper-V when using default network-image.png

    Cannot connect to network in Hyper-V when using default network-image.png

    That's it.

    Note   Note
    To connect to remote Hyper-V host, both your primary host and remote host must have WinRM service running and Trusted Hosts list on both hosts must contain both computers.

    Prerequisites are exactly the same than in using Windows Admin Center to connect to remote computers. See Part One in this tutorial to set both computers up correctly: Windows Admin Center - Centrally manage all your Windows 10 PCs | Windows 10 Tutorials

    Step 3.9 in above mentioned tutorial will show some troubleshooting tips if you cannot add remote hosts in Hyper-V Manager.

    This way, you can connect to any VM on remote host, with normal or enhanced mode. This basically makes RDP unnecessary.

    Kari
      My Computer


  8. Posts : 16,623
    Windows 11 Pro X64
       #8

    I didn't know about the bandwidth bug. I'm making a bunch of VMs at work. I will test it and see if it effects me.
      My Computers


  9. Posts : 17,661
    Windows 10 Pro
       #9

    Dude said:
    I didn't know about the bandwidth bug. I'm making a bunch of VMs at work. I will test it and see if it effects me.
    I am not sure if the 1803 official release has this bug, but I get it both in Skippy and normal Fast Ring Insider builds.
      My Computer


  10. Posts : 15,441
    Windows10
    Thread Starter
       #10

    Kari said:
    I am not sure if the 1803 official release has this bug, but I get it both in Skippy and normal Fast Ring Insider builds.
    Yep - it started with 1803.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:43.
Find Us




Windows 10 Forums