networking - How to set static IP address on Window 8.1 Host with Hyper-V and Single network adapter

06
2014-04
  • Scott Forbes

    I have a Windows 8.1 Pro machine (not preview). In order to do Windows Phone 8 development, the emulators have to use the Hyper-V engine to run. When Hyper-V was installed it changed my network adapter settings for my ethernet card to utilizing the Hyper-V virtual switch, and disabled all the other items, such as IPv4, etc. It appears I can no longer set a static ip address on my box for my LAN, or at least it is not evident how to do it.

    Articles that I have read suggest that I need two network adapters, but they seem to be geared towards a different type of infrastructure, which is different than what I am doing. I do not wish to purchase another network adapter. I simply want a static IP address on my box as my router is configured to route certain types of traffic to my box, and utilize Hyper-V just to run the Windows Phone emulators, but the emulators still have to access the internet.

    • Answers
  • jay

    I was facing the same issue as you were, I solved it by setting the static IP address in the vEthernet instead of the Ethernet.


    • 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
  • 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.

  • 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.