This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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?
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
Please post the results below from both
tracert 8.8.8.8
ipconfig /all
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
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.
Here is the ipconfig /all output from the Windows 10 VM:
Windows IP Configuration
Host Name . . . . . . . . . . . . : DESKTOP-BARGUKO
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mshome.net
Ethernet adapter Ethernet 3:
Connection-specific DNS Suffix . : mshome.net
Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter #3
Physical Address. . . . . . . . . : 00-15-5D-2C-17-05
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::f067:964b:106a:8a9a%15(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.137.122(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, January 25, 2022 12:58:52 PM
Lease Expires . . . . . . . . . . : Monday, January 31, 2022 12:40:06 PM
Default Gateway . . . . . . . . . : 192.168.137.1
DHCP Server . . . . . . . . . . . : 192.168.137.1
DHCPv6 IAID . . . . . . . . . . . : 268440925
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-72-59-73-00-15-5D-2C-17-01
DNS Servers . . . . . . . . . . . : 192.168.137.1
NetBIOS over Tcpip. . . . . . . . : Enabled
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--
They are not using a default switch, they are both using an external switch that I've already created. I created the Windows Server 2016 VM yesterday, and noticed that I did not have Internet in that VM, though I was able to access the internet from the Windows 10 VM. Again, the Windows 10 VM has been connected to the Internet for several days up until this morning.
Here is a screenshot showing that I only have one external virtual switch for use:
Note also that yesterday, I removed the network adapter from the Windows Server 2016 VM and reattached it: no difference.
I then deleted the external virtual switch I had yesterday and recreated it: the Windows 10 VM remained connected to the Internet (again, until today), and the Windows Server 2016 VM could still not connect.
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--
Okay, would you mind elaborating a little bit on how I can fix this?
I can tell that the 169.254.xxx.xxx address is APIPA which means it's not receiving DHCP IP; I wasn't aware that the 192.168.137.xxx address space belonged to the default switch.
We had a set up with two hosts before, each using an external virtual switch for VM connectivity that worked without any problems right out of the box. We recently upgraded our machines and tried to redeploy our hosts from scratch... we set up the external virtual switch the same exact way that we had it configured on the last deployment, but we've run into these issues now.
Seeing as networking just kind of "worked" last time, I'm not understanding why there are issues occurring now, and I certainly don't know how to fix these things.
We do have a DHCP server on the same network as the Hyper-V hosts, but again, I never had to do any explicit configuration for networking like this.
We do have a DHCP server on the same network as the Hyper-V hosts
Then I'd probably compare an ipconfig /all of some other physical working pc to the results above.
I have attached the output of ipconfig /all from the Hyper-V host that is running the VMs in question.168522-ipconfigall.txt
To answer your questions:
tracert 8.8.8.8 on the Windows Server 2016 VM with no Internet:
ipconfig/all on 2016VM: