Windows 10: Win10 hyper-v cannot connect to internet. Vm can only ping router!

  1.    27 Dec 2015 #1

    Win10 hyper-v cannot connect to internet. Vm can only ping router!

    I have installed a Win10 Hyper-v machine in my windows 10 system and cannot get this thing to connect to the internet
    I can get as far as the router, in other words from the VM I can ping the router; in reality it doesn't matter what IP address I try to ping, if I ping it still takes me to the router log in screen. So I might be close but don't know how to proceed.

    My set up is a RealTek GBE physical NIC, with an External switch, changed all IP addresses on the switch to be within the LAN IP address's range, I set the virtual NIC inside the Win10_VM to be within the LAN IP address range of the host's physical NIC as well, still no connection,

    It has taken me a lot of pain work and frustration to be able to get this far; so many dead ends, and still this darn hyper-v thing cannot connect to the internet. Why is this so difficult to accomplish?

    It is so frustrating , I believed I have tried all configurations I can think of and this is the only configuration that got me the closest to an Internet connection. Please help!

    I tried, Internal switch with the host NIC sharing a connection to the VM-Switch, I have tried bridging both NIC and vEtherNet card, in both configurations External and/or internal and many more other things I've tried. Nothing has worked no matter what.

    Thank you. please help

      My ComputerSystem Spec

  2. Kari's Avatar
    Posts : 15,009
    Windows 10 Pro
       28 Dec 2015 #2

    Hi Gorgonio, welcome to the Ten Forums.

    Hyper-V is easy and straight forward to set up when done correctly. You enable the Hyper-V feature, create an external virtual switch, install a guest OS selecting the external switch as connection and you are done.

    There's no need to set static IP addresses. Of course you can use a static IP if that's what you prefer but Hyper-V virtual machines work just fine with DHCP and dynamic IP addresses.

    There is never need to manually create a network bridge. If you create an external switch using the host's wireless NIC, Hyper-V automatically creates a network bridge. With wired host NIC (Ethernet), the bridge is never needed nor should it be made.

    Seems that your setup is totally screwed, I recommend to either restore a System Image or do a System Restore to the point before before you set up Hyper-V and start from scratch. You can try to remove all your network switches using the Hyper-V Virtual Switch Manager and manually removing all network bridges, then reboot and try creating the switches again, but I doubt this will work.

    Tutorial: Hyper-V virtualization - Setup and Use in Windows 10 - Windows 10 Forums

      My ComputerSystem Spec

  3. Posts : 52
    Windows 10 Pro x64 version 1703
       29 Jan 2016 #3

    Failed to create a Hyper-V virtual switch

    Hello Kari,

    Your excellent posts are a great help! Thank you!

    However: there seems to be a problem. Up to build 10586 I have successfully used VM's with a virtual switch connected to my wireless adapter. Then I updated to build 11102. The virtual switch then was disappeared. What is worse, I could not create a new one, at least not one that is connected to the wireless adapter. I get the following error: see attachment.

    I have never created a bridge manually. When I try to bridge my wireless and my ethernet together, I get the following error: see attachment. Not very helpful. I know it is not a supported configuration, but it is just as a demonstration.

    Am I doing something wrong? Or is it a bug in this build?


    Attached Thumbnails Attached Thumbnails 2016_01_29_21_23_321.png   2016_01_29_21_25_502.png  
      My ComputerSystem Spec

  4. Kari's Avatar
    Posts : 15,009
    Windows 10 Pro
       29 Jan 2016 #4

    BartZorn said: View Post
    I have never created a bridge manually. When I try to bridge my wireless and my ethernet together, I get the following error: see attachment. Not very helpful. I know it is not a supported configuration, but it is just as a demonstration.
    First: The Bridge needed for the wireless external switch is not supposed to bridge the Ethernet and wireless adapters! You have the concept a bit wrong.

    This extract from a tutorial Hyper-V Virtual Switch Manager on our sister site the Eight Forums:

    You might have also noticed that although the virtual switch vEthernet is connected to (is using) host’s WLAN NIC it is however showing an Ethernet LAN symbol (connector of a LAN cable) and presented under LAN connections. This has a simple explanation: all Hyper-V network connections are Ethernet (LAN) connections; Hyper-V does not support WiFi so even when a virtual switch is connected to a wireless NIC, Hyper-V presents it as Ethernet connection to the virtual machine i.e. the virtual NIC on vm “thinks” it is connected with an Ethernet cable.

    This also means that when we are using an external virtual switch connected to a WLAN NIC, we need an extra network bridge on the host. The virtual NIC connects to a virtual switch, virtual switch in its turn connects to a host network bridge which creates (as its name says) a bridge between our virtual Ethernet connection and host WLAN NIC’s connection to the router:

    Click image for larger version. 

Name:	15815d1359693033-hyper-v-virtual-switch-manager-virtual_switch_16.png 
Views:	1 
Size:	30.1 KB 
ID:	61476
    (Note: NIC = Network Interface Controller, the network adapter. WLAN NIC = wireless adapter.)

    Hyper-V does not have any emulated virtual hardware for a wireless connection. Therefore it handles even an external wireless switch as a wired Ethernet connection. The host needs a bridge between the wireless switch and the real physical WLAN NIC; it kind of "translates" the wired network traffic coming from vm to the wireless host NIC. This bridge will be automatically created when a wireless external switch is created, there's no need to do it manually.

    To start with, please tell if the wireless external switch is still present in your system although not shown in Virtual Switch manager. You can check it in PowerShell with following command (or rather cmdlet as they are called in PowerShell):

    It shows all present virtual switches:

    Click image for larger version. 

Name:	59689d1453247042-hyper-v-virtualization-setup-use-windows-10-a-2016_01_19_23_43_573.png 
Views:	1 
Size:	35.6 KB 
ID:	61478

    Post the same screenshot as shown above as an example, we'll start from that.

      My ComputerSystem Spec

  5. Posts : 52
    Windows 10 Pro x64 version 1703
       30 Jan 2016 #5

    First: I know that I am not supposed to bridge my two network adapters together. I only tried that to show that there may be a problem with bridges anyway. I read a post somewhere that bridging the two together might be a solution to the problem of not being able to connect the wireless adapter to a virtual switch. He/she also told me that it is definitely not a supported configuration.

    The Get-VMSwitch gives me the following:

    Name SwitchType NetAdapterInterfaceDescription
    ---- ---------- ------------------------------
    Hyper-V Virtual Switch External Realtek PCIe GBE Family Controller

    This switch works OK for my VM's as long as I have a network cable attached.



      My ComputerSystem Spec

  6. Kari's Avatar
    Posts : 15,009
    Windows 10 Pro
       30 Jan 2016 #6

    BartZorn said: View Post
    The Get-VMSwitch gives me the following:
    OK so the wireless switch is totally gone.

    A workaround if you are unable to create an external switch with the wireless adapter is to create an internal switch, set the vm to use it, and share the host wireless connection with that internal switch.

    See this post for more information about the workaround: Hyper-V virtualization - Setup and Use in Windows 10 - Page 28 - Windows 10 Forums
      My ComputerSystem Spec

  7. Posts : 52
    Windows 10 Pro x64 version 1703
       30 Jan 2016 #7

    Yes, I tried that already. The BIG disadvantage is that that creates an extra NAT layer with all its problems. For instance: when I have more than one VM behind NAT, I cannot reach file services from all of them unless I change the default port numbers. Plus, the sharing configuration only shows applications, not port numbers. I have not found out how to disable NAT but keep the router functionality in ICS.

    Do you have any idea what might be the reason I can't do what I want, although I could with earlier builds?


      My ComputerSystem Spec


Related Threads
connect router in Network and Sharing
how to connect router to a cable all in one modem
I know that propably it's not a Windows 10 related topic but I didn't know where else to ask that. I searched a bit on the Internet for a solution and I couldn't find any. So whenever my brother opens his laptop and connects to the Wifi every...
I had a few problems with my PC, so I refreshed it. After doing that, I was not able to connect to my virtual router plus, nor find a wireless adapter. I have literally tried everything but I can't fix it. I've attached a picture of my available...
I thought it was a driver issue but I've updated drivers afaik and still no joy. The router is sitting a metre away from me but the HP Probook 4730s cannot see it. It sees my 5 neighbours' routers but not mine. I need ideas on what to look at to fix...
My first upgrade ended in failure. The second time, I removed my wifi adapter and it installed successfully. I reinserted my wifi adapter, it only detects my neigbours router. Anyone here have similar issues? The wifi adapter is a D-LINK DWA-125...
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 20:47.
Find Us