networking - Windows 8 Hyper-V network not working on host

04
2013-08
  • Ryan

    I have carefully followed the instructions in the first answer, but I still can't get the network adapter to be shared with the host operating system. My symptoms appear to be identical to this question, but a reboot did not fix the issue. Networking works fine for my VMs, and it's connecting to the wireless network, but I cannot get access to the Internet from my host OS.

    It appears that this guy is having the same problem, but he hasn't said anything for a few days.

    Here is a screenshot of my virtual switch configuration when I have it turned on: Hyper-V virtual switch settings

    • Answers
  • Graham Wager

    I would recommend against using a wireless connection with Hyper-V, as it can cause no end of issues when trying to connect to networks.

    You could try changing your Hyper-V network to an Internal network:

    enter image description here

    This appears as a new virtual network adapter in your host:

    enter image description here

    Then depending on your needs, either enable Internet Connection Sharing on your wireless adapter:

    enter image description here

    or bridge the new internal adapter and your wireless one (ignore that this screenshot shows two virtual networks):

    enter image description here


    • Related Question

    networking - Two Network Adapters on Hyper-V Host - Best way to configure?
  • GoNorthWest

    I have two physical network adapters installed in my Hyper-V host. I want one to be dedicated to the host, and the other to provide external network services to the VMs. Would the appropriate configuration be as such:

    • Leave the first physical network adapter alone, assigning it the host IP, but not using it to create any Virtual Netorks
    • For the second physical adapter, I would create an External Network, along with a Microsoft Virtual Switch, and use that to provide network services to the VMs. Each virtual NIC for the VM would be associated with that External Network. A static IP would be assigned to this adapter, and each VM would be assigned a static IP as well.

    The above seems reasonable to me, but I'm not sure if it's correct. Does anyone have any thoughts?

    Thanks!

    Mark


    • Related Answers
  • Marty

    That sounds like the best way to configure a system with two adapters. But if I'm understanding what you typed, you don't need to configure a static IP to the second adapter if you don't want. Don't be surprised when you look at the properties of the second NIC and IPv4/IPv6 are not bound to it, it should only have the 'Microsoft Virtual Network Switch Protocol' bound to it.

  • john

    The way I understand it, you would be missing out on available transfer speeds doing it this way. Each virtual switch is mapped to a physical NIC:

    External virtual networks. Use this type when you want to provide virtual machines with access to a physical network to communicate with externally located servers and clients. This type of virtual network also allows virtual machines on the same virtualization server to communicate with each other. This type of network may also be available for use by the management operating system, depending on how you configure the networking. (The management operating system runs the Hyper-V role.) For more information, see “A closer look at external virtual networks” later in this topic.

    [Microsoft TechNet: technet.microsoft.com/en-us/library/cc816585(v=ws.10).aspx]

    With this in mind, you could set up two virtual switches, each mapped to a physical NIC, or you could team (trunk, combine) the NICs and have one virtual network. Either way,with only two physical NICs you would probably be losing out if you dedicated one to management of the Host.