You would have to reinstall VMware tools on the VM. However you could follow the steps mentioned below to reinstall.
1. Removed VMNET3 NIC
2. Started VM and ran "netsh int ip reset c:\resetlog.txt" (to delete old/ghost configs), make the ghosted network adapter visible in the Device Manager and uninstall the ghosted network adapter from the registry.
3. Stoped VM and added VMNET3 (enabled but disconnected)
4. Started VM and configuerd IPv4-static+Gateway+DNS
5. Stoped VM and set VMNET3 to be "connected"
6. Started VM... all works fine now for 3 days without issues.
Steps to make the ghosted network adapter visible in the Device Manager and uninstall the ghosted network adapter from the registry:
Click Start > Run.
Type cmd and press Enter.
At the command prompt, run this command:
Note: open the command prompt using the Run as Administrator option.
Start the Device Manager by running this command from the same command prompt:
Click View > Show Hidden Devices.
Expand the Network Adapters tree (click the plus sign next to the Network adapters entry).
Right-click the dimmed network adapter, then click Uninstall.
Once all of the grayed out NICs are uninstalled, assign the IP address to the virtual NIC.
I was still seeing odd network behaviour even after a reinstall of VM tools, so have now carried out your additional steps, and will monitor for improvement for a few days.
Thank you for updating the post
Unfortunately, this hasn't helped. I still had a reset, and my application keeps reporting drops in connectivity!
Any further thoughts on what I can try?
Could you please post your ESXi version and a build number?
I am seeing VMXNET3 resets in our lab on a Windows 10 1803 VM and Server 2012R2.
We are on VMware ESXi 6.0 U3 Dell Version: A10, Build# 7967664
I'm running6.5.0 Update 1 (Build 5969303)
Are you able to tweak the global nic settings as suggested in the post?
Upgrade to latest VMTools version 10.2.5 (vmxnet3 driver 126.96.36.199) and see if the issue is seen?
Have updated to both ESXi 6.7 and the latest build of tools.
So far, everything seems ok, but it was an intermittent issue before so not guaranteed fixed yet.
I haven't seen any resets for about 8 days now, so am fairly confident that the update of the tools/vmxnet3 driver has resolved my issue!
I am having the same issue. ESXi 6.5 U2 GA, Windows 10 1607 clients. I currently have clients running vmxnet3 driver 188.8.131.52 and 184.108.40.206 that experience resets, so upgrading to the newer Tools version is clearly not the resolution by itself.
Running vmware tools 10.2.5 and i am still having resets on windows 2016 servers. any other thoughts? a case has been logged to vmware as well on this.