Hyper-V Internet access on one VM but not the other

Delaney Horton 21 Reputation points
2022-01-24T21:17:07.427+00:00

I have two VMs residing on my Hyper-V host. One is a Windows 10 and the other is a Windows Server 2016 instance.
I have one external switch created and it is attached to both of the virtual machines.
The Windows 10 VM is able to access the Internet, but the Windows Server 2016 VM cannot.
I have tried removing the switch from the VM and adding it back, but it doesn't make a difference.
How could this be the case when they are both using the same external virtual switch?

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,560 questions
0 comments No comments
{count} votes

11 answers

Sort by: Most helpful
  1. Dave Patrick 426.1K Reputation points MVP
    2022-01-25T21:37:49.47+00:00

    I think the external vSwitch is tied to the wrong network interface. If the host has internet access then it's got to be via QLogic BCM5709C Gigabit Ethernet (NDIS VBD Client) #35 (Ethernet adapter Ethernet 5 10.195.44.1 network) since that's the only interface with a default gateway address.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  2. Dave Patrick 426.1K Reputation points MVP
    2022-01-26T18:48:34.37+00:00

    Ok, well then it looks like the addressing may be incorrect for that guest. From what I can tell the default gateway is 10.195.44.1

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  3. Dave Patrick 426.1K Reputation points MVP
    2022-01-26T20:08:33.013+00:00

    How do you suggest that I go about fixing this?

    Delete / recreate the external vSwitch, just make sure it's on the correct network ( presumably 10.195.44.1)

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  4. Dave Patrick 426.1K Reputation points MVP
    2022-01-27T19:09:13.827+00:00

    This shouldn't be that difficult. The simplest solution may be to remove both vSwitches, then add back a single vSwitch, trying each adapter until you get it.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  5. Delaney Horton 21 Reputation points
    2022-01-31T20:05:11.643+00:00

    @Dave Patrick I figured out why the VMs were not receiving the proper IP information when the virtual switch was attached the proper network adapter.
    I went to the location that the hosts were physically being kept, and discovered that the host being used for AD/DHCP/Storage services was down due to a failed disk. After replacing the disk, reconfiguring RAID and restoring from a recovery point, the OS is back up and functional.
    After rebooting the Hyper-V host, the virtual machines were able to receive the properly IP config to access the internet via the external virtual switch.

    This was not a Hyper-V issue it turns out, but an issue of not being able to contact the DHCP server due to disk failure.
    Thank you for your time and patience while troubleshooting this.