NAT resolution on VMware not working - DNS_PROBE_FINISHED_BAD_CONFIG

[Nexxsys]

What's the problem?

After the installation script is completed (Network Adapter in VMWare Workstation set to NAT pre, during, and post installation script execution) the VM can not longer resolve domains. Error: DNS_PROBE_FINISHED_BAD_CONFIG I the network adapter is switched to Bridged all is good. I have also created a Mandiant Commando VM with no issues, same base windows VM for both installation scripts.

Steps to Reproduce

Set Network Adapter to NAT
Try to resolve any web address or ping in terminal/powershell or command prompt.

Environment

VMWare Workstation Pro 17.5.2 build-23775571

Additional Information

Error: DNS_PROBE_FINISHED_BAD_CONFIG

[emtuls]

Hi @Nexxsys!

Could you please provide some of the logs that were created during the install as well as what OS version you are using?

I will try to look into this and see if I run into the same issue on a fresh install with a new Windows 11 VM on VMWare, but this seems to be an issue that is not uncommon outside of FlareVM so I'm unsure if our installer is causing this, though I will certainly take a look. :)

[emtuls]

@Nexxsys Unfortunately, I was unable to reproduce this issue on a new Windows 11 VM in VMWare Workstation.

I can attempt to look at your logs when you post them to see if I may be able to determine what the issue is, or this may just be a Windows issue. Fortunately, it seems that it can be resolved easily by one of the following commands in a command prompt (followed by a restart):
netsh int ip reset
or
ipconfig /flushdns