VMNAT.EXE Bug? VMWare 17.0.2 to 17.5.0 - change in network behavior

[htoh]

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)

[htoh]

a bump up

[htoh]

can we classify this as a VMNAT.EXE bug for fix in next version?

[VirtualJeffJ]

I recently purchased VMware Workstation Pro 17.5 and have this same issue. I lose DNS after 5 minutes to 10 hours. I can still ping IP addresses on the Internet, but a host name will not resolve. It works if I have a local hosts file, but I cannot add hundreds of entries for what I need.

To get going again, I have to stop and start the vmnat.exe service and then do an ipconfig /release and /renew on each VM to get them working again. I have had this happen while I was using one of the VMs, so it has nothing to do with sleeping and waking for me.

Where can I get the vmnat.exe 17.0.2? 

Thanks.