VMware Workstation

 View Only
Expand all | Collapse all

Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

  • 1.  Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

    Posted Oct 20, 2023 02:50 PM

    I upgraded from 17.0.2 to 17.5 on my Windows 11 Pro 22H2  based device today.   After completing the upgrade I can no longer get my VMs to connect to the default NAT.  Multiple reboots of the host do not make a difference or upgrading VMWare Tools on the VMs (Windows 10 Enterprise 22H2))



  • 2.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

    Posted Oct 23, 2023 07:45 AM

    I have the same problem.  Do you solve this problem?



  • 3.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs
    Best Answer

    Posted Oct 23, 2023 10:29 AM

    Hi  

    Please provide below details as the issue did not repro from our end. 

    1. Are you facing issue only in NAT mode? Bridge mode is working fine? If so please try out a clean installation of WS 17.5 
    2. If the issue exists in NAT mode only, are they able to get IP in VMs? ping works between host and VM ?
    3. Please provide VM support bundle. (Select VM >> Help >> Collect Support data ..)
    4. Please provide the ISO used for Win10-Enterprise 22h2 version
         - I have downloaded from official website(https://www.microsoft.com/en-in/software-download/windows10) and no repro from our end. I used Windows 10 Pro edition
         - Host - Win11 22h2, GuestVM - Win10 22h2

    Clean Install Workstation Pro/Player:
    -----------------------------------------------
    1) Uninstall WS Pro/Player.
    2) Go to this location - C:\ProgramData\VMware and delete the folders for VMware Workstation and VMware Player.
    3) Go to this location - C:\Users\dtomar\AppData\Roaming\VMware and delete all the files inside
    4) Go to this location - C:\Program Files (x86)\VMware and delete the folders for VMware Workstation and VMware Player.
    5) Install WS Pro/Player

    Thanks,



  • 4.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs
    Best Answer

    Posted Oct 24, 2023 02:33 PM

    This worked in my situation:

    Clean Install Workstation Pro/Player:
    -----------------------------------------------
    1) Uninstall WS Pro/Player.
    2) Go to this location - C:\ProgramData\VMware and delete the folders for VMware Workstation and VMware Player.
    3) Go to this location - C:\Users\dtomar\AppData\Roaming\VMware and delete all the files inside
    4) Go to this location - C:\Program Files (x86)\VMware and delete the folders for VMware Workstation and VMware Player.
    5) Install WS Pro/Player



  • 5.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

    Posted Oct 26, 2023 08:17 PM

    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.



  • 6.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

    Posted Oct 26, 2023 09:40 PM

    This workaround solved my issue.
    Thanks to 



  • 7.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

    Posted Nov 03, 2023 12:03 PM

    This resolved the NAT issue(s) for my install too. No more high CPU on my ThinkPad x280 as well.
    Thank you



  • 8.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

    Posted Nov 24, 2023 07:43 PM

    I tried:

    - Uninstall VMware Workstation, clean folders, reinstall

    - Replace vmnat.exe with the 17.0.2 version

    I'm still without network in my 17.5 VMs set as NAT.

    Guess I'm stuck using bridged networking for a good while.



  • 9.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

    Posted Dec 28, 2023 06:39 PM

    Because I randomly lose DHCP or DNS or both so frequently on NAT'd VMs, I now have a script:

    net stop "VMware NAT Service"
    net stop "VMnetDHCP"
    net start "VMware NAT Service"
    net start "VMnetDHCP"

    I run this as a scheduled task multiple times a day, and on-demand if my fans kick on or I lose DNS or DHCP.

    I really hope I can get rid of it soon.



  • 10.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

    Posted Jan 03, 2024 10:37 AM

    I have the same problem with 17.5 on my VMs. Restarting "VMWare NAT Service" every hour.

    I worked with 12.5 for nearly ten years perfectly fine and Upgraded to 17.5.
    But i con not adress this problem to vmware, because i am not connected with the main account, and dont know how to fix this.



  • 11.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

    Posted Jan 09, 2024 02:22 PM

    I am still having this that after a while all my VM's network connectivity over the host system fails.

    VM-ware: 17.5

    Host: Windows 11H2 enterprise host machine.

    Guests: Windows 10 Pro 22H2, Ubuntu 22.04

    This work-around resolved it temporary without reinstall of VM workstation Pro 17.5 or restarting even the VM's.

    net stop "VMware NAT Service"
    net stop "VMnetDHCP"
    net start "VMware NAT Service"
    net start "VMnetDHCP"

     

     

     

     

     

     



  • 12.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

    Posted Feb 27, 2024 03:28 AM
      |   view attached

    Why is this possible?

    - VMware NAT service is 24% CPU

    - VMware Workstation VMX is 5.1% CPU

    More of my machine is doing the NAT than doing the work!

    As I was grabbing this screenshot, the NAT service jumped up to 30% while the VMX was at 0.9%. Wish I had grabbed that screen shot in time.



  • 13.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

    Posted Apr 02, 2024 08:33 AM

    Hello,

    I applied to workaround to use the vmnat.exe version 17.0.2 on my 17.5.1 VM Workstation Pro installation. This cured for now the exact symptoms as described.

    Of course VM needs to check what is the difference in code between 17.0.2 and 17.5.1 vmnat.exe.



  • 14.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

    Posted Apr 02, 2024 02:00 PM

    I've been using vmnat.exe 17.0.0 build-20800274 without issue on Workstation Pro 17.5.1 



  • 15.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

    Posted Oct 25, 2023 12:23 AM

    These suggestions did not work in my case. I had to uninstall 17.5 and reinstalled 17.0.2 before I could have internet in the VMs.

    Below are my issues:
    After upgrading from 17.0.2 to 17.5, I noticed that the VMs could not access the internet.
    The VMs did receive IP addresses from NAT.
    I could ping the VMs from the host.
    I could ping the host from the VMs.
    I couldn't ping the NAT gateway from the VMs.
    The bridge network was working.



  • 16.  RE: Post 17.0.2 to 17.5 upgrade results in no networking (NAT) for VMs

    Posted Oct 25, 2023 05:32 PM

    Did you attempt the clean install (all steps, not just uninstall from control panel) as others and myself have reported as working?