- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unable to do internal debugging in the "VMware NAT Service", I did this action to resolve my problem.
It is clear that there is a conflict on the my 2 DELL laptops that I own with the new executable "vmnat.exe".
Even by doing a complete clean of files and registry in system mode, nothing fixed my problem except the workaround that I applied on my laptops.
I hope a future version will fix my problem.
workaround:
Copy the "C:\Windows\SysWOW64\vmnat.exe" to the "%userprofile%\Desktop".
launch the update to version 17.5 execute the update.
Stop the “VMware NAT Service” service
rename the file "C:\Windows\SysWOW64\vmnat.exe"
copy the "%userprofile%\Desktop\vmnat.exe" to "C:\Windows\SysWOW64"
Start the VMware NAT Service
My problem is fixed, no more malfunction of the "VMware NAT Service" service, communication from the VM to its default gateway is restored.