VMware Communities
peter_l1
Contributor
Contributor
‎09-16-2020 12:23 AM

Host upgrade to Windows 10 2004 and loss of host only and NAT networking after suspend or hibernate

I have upgraded my host from Windows 1909 to 2004 and now I have noticed that when my host OS suspends or I hibernate it then I am no longer able to communicate with any of the guest VMs.

The guest VMs when on NAT can still ping the .2 NAT IP and can access the internet.

If I change to bridged networking then shutdown the interface and bring it back up again with an IP on that network I can ping the local network.

The host is Windows 10 2004, and the guest are RHEL 7.8, Windows and Debian images all have the same problem.

I have tried doing a complete uninstall of Workstation 15.5.6, and just upgraded to Workstation 16 just in case it is fixed it but it hasn't.

The only thing that has changed was the upgrade of the Host to 2004, and I have foolishly removed the 1909 backup so I can't go back.

Any suggestions on what I could do other than a full re-install of Windows for the host which I would rather not do.

Reply
0 Kudos
2 Replies
yanw
VMware Employee
VMware Employee
‎09-16-2020 01:05 AM

I have a Win 10 2004 Host (19041.508) with VMware Workstation 16 installed. I changed the "Control Panel\Hardware and Sound\Power Options" and select the host to hibernate when press power button. Then I press the host power button to hibernate the windows host and press the power button again to bring it back. However can not reproduce your issue.

Would you please have a check if the "Ethernet adapter VMware Network Adapter VMnet1" and "Ethernet adapter VMware Network Adapter VMnet1" can be seen through the "ipconfig /all" output?

Reply
0 Kudos
peter_l1
Contributor
Contributor
‎09-16-2020 12:11 PM

I think I have found the problem and it is to do with the arp cache not sending out an ARP request for the guest VMs IP.

If I have a command prompt in my hose attempting to ping my guest and then I sleep my laptop then as soon as it comes back I get request timed out. But the host isn't sending out an ARP request for each ICMP request when the address is known.

Then after about 1 min I finally see an arp request from the host as shown in packets 3&4 as wireshark stops capturing when you sleep / hibernate and then the host can ping the guest.

ICMP.png

I have also applied all bios, other firmware and driver updates to the Toshiba laptop.

But doing a ping once I resume from hibernate or sleep does seem to bring the host back, and this has only started since I upgraded to Windows 10 2004 as I have not had this problem prior.

And further on this, it seems that it can take up to 60 seconds or more of constant pinging for the host to kick off an arp request. If I delete the arp cache, or start a continual ping from both the host and guest.. it seems to figure itself out.

Reply
0 Kudos