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,267 questions
0 comments No comments
{count} votes

11 answers

Sort by: Most helpful
  1. Philippe Levesque 5,086 Reputation points MVP
    2022-01-24T21:46:28.45+00:00

    Hi

    Please compare the IP configuration and try to check if the server is static versus an DHCP lease maybe from the Windows 10.

    nb; If the server is static, try it on DHCP to see if it can get a lease

    0 comments No comments

  2. Dave Patrick 389.5K Reputation points MVP
    2022-01-24T21:56:45.46+00:00

    Please post the results below from both
    tracert 8.8.8.8
    ipconfig /all


  3. Delaney Horton 21 Reputation points
    2022-01-25T18:07:08.567+00:00

    Something new that I've just noticed today: the Windows 10 VM is now not connecting to the Internet either, though I know for a fact that it has been connected for several days leading up to now.

    Here is the tracert output on the Windows 10 VM today:

    Tracing route to 8.8.8.8 over a maximum of 30 hops
    
      1     *        *        *     Request timed out.
      2     *        *        *     Request timed out.
      3     *        *        *     Request timed out.
      4     *        *        *     Request timed out.
      5     *        *        *     Request timed out.
      6     *        *        *     Request timed out.
      7     *        *        *     Request timed out.
      8     *        *        *     Request timed out.
    

  4. Dave Patrick 389.5K Reputation points MVP
    2022-01-25T18:18:00.307+00:00

    both using the same external virtual switch?

    This looks more like both using a default switch on windows 10. Might try creating an external vSwitch and connecting guests to it.
    https://blogs.technet.microsoft.com/jhoward/2008/06/17/hyper-v-what-are-the-uses-for-different-types-of-virtual-networks/

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


  5. Dave Patrick 389.5K Reputation points MVP
    2022-01-25T18:29:01.84+00:00

    Sorry, only looked at the second one which uses the same address space as the default switch (192.168.137.xxx) which is likely problematic. The first one got an APIPA address (169.254.xxx.xxx) which simply means there was no DHCP server available on the connected network.

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