- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
VMNAT.EXE Bug? VMWare 17.0.2 to 17.5.0 - change in network behavior
At version 17.0.2:
Host: Windows 11
Guest: Windows 10, 11
Network: DHCP -- host (VPN) -- VMWare Guest (vmxnet3 - NAT)
Behavior: Works normally, sleep, wakes, works normally
At version 17.5.0:
New Behavior: Works normally, sleep, wakes, DNS calls fail
Immediate Workaround: (vmxnet3 - bridged), but VPN is bypassed
This change in behavior occurs with VMWare Tools 12.3.0 and 12.3.5
Can anything be done to make NAT work with VPN (after sleep and wake)?
Additional Information:
What did not work: Restarting VM NAT Service
What worked: Restarting VM NAT Service after file replacement - vmnat.exe (version 17.5.0) changed to vmnat.exe (version 17.0.2)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a bump up
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
can we classify this as a VMNAT.EXE bug for fix in next version?