I’m trying something apparently very simple, and I reviewed former posts for 2 days about the subject without success:

  • Setup a Hyper-V Server 2019
  • On that server, install a Gen-2 guest Virtual Machine (Windows server 2016 standard)
  • That's ALL !

I have been assured by written (by Dell) that the hardware I bought 3 months ago is fit for virtualization…

Setting up a Hyper-Server, and joining it to a domain was pretty straight forward. Even installing the VM was pretty simple.

But I just can’t get the guest VM to connect to the network!

Here is the current state, after I re-started from scratch (meaning reinstalled the computer from zero), and left the default, as generated by Microsoft:

The Host does have access to internet (and is linked to AD) on ethernet NIC#1

  • Assigned Static IP:
  • Subnet:
  • gateway:
  • DNS:

From a remote Hyper-V manager (because Hyper-V Server has no GUI), I did create a new Virtual Switch (and only one)

  • Name: vSwitchExternXyz
  • Type: external
  • Linked to the external network using the same NIC#1
  • Allowed management operating system to share this network adapter (this is by default)

When executing an "ipconfig" in command line on the host, I see a new “Ethernet adapter vEthernet (vSwitchExternXyz)” this created, having:

  • Autoconfiguration IP4 Address: (hey, this is a APIPA address !)
  • Subnet:
  • gateway: none!

From the remote Hyper-V manager, I did assign this vSwitchExternXyz Virtual Switch (the only one I created in the Host) to the guest VM

  • I left unchecked both options “Enable virtual LAN identification” and “Enable bandwidth management” (those are unchecked by default)

When I start & connect to that only VM, and look at it network config, I get:

  • Autoconfiguration IP4 Address: (again another APIPA address!)
  • Subnet:
  • gateway: none!

From that picture, I’m not really surprised I cannot even ping any IP outside the APIPA address range, because the default gateway seems missing. I did try to assign it an IP and valid gateway (same as the host’s), but it made no differences. But I don’t know yet how should a successful configuration looks like.


  • I have no running environment to compare to in order to see if those defaults are correct. Do the virtual switch & VM’s vNIC adapter both should be given IP addresses?

  • Shouldn’t both virtual switch & VM’s vNIC adapter be in the same subnet than the host (meaning 192.168.0.x), and pointing to the same gateway?

  • What’s wrong with my VM to not access internet?

  • Did you read the Hyper-V documentation on how to configure the NIC of a guest ? Do you want the guests to be part of your host's network or not ?
    – Overmind
    Jan 30, 2020 at 7:02
  • Yes I did read the Hyper-V documentation on how to configure the NIC of a guest. And I do want the guest to be on the same network segment than the host.
    – ChristianT
    Jan 30, 2020 at 20:10
  • Simply selecting the guest network adapted as default VS Switch should obtain your desired result.
    – Overmind
    Jan 31, 2020 at 7:00
  • You are correct Overmind, But the vSwitch did not attach correctly to the physical NIC (for unknown reason). and it got a dummy APIPA ip instead of the one for from the connected NIC of the host
    – ChristianT
    Jan 31, 2020 at 23:38
  • Do you have DHCP on your network? Because if not, then the NICs will not just configure themselves. You have to manually configure a static IP address (and DNS, and gateway) to them, and I don't see anything like that in the steps you described.
    – Massimo
    Jul 23, 2021 at 21:04

1 Answer 1


I resorted to Microsoft support to address this issues (it took 2 tech specialists 2.5 hours total to figure it out).

The problem was with the virtual switch which was corrupted for obscure reasons.

It was not enough to just remove the vSwitch and re-create it.

I had to:

  • leave the faulty vSwitch there,
  • create a new vSwitch
  • Assign the new switch to the Guest VM's adapter
  • only then, delete the faulty vSwitch

Problem fixed, thanks to Raj at Microsoft technical support team.

  • Yes, creating a new one and deleting the old one is the next logical step. Such an issue should not normally happen, though.
    – Overmind
    Feb 3, 2020 at 6:15

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .