VMware Workstation 16 Pro Guest can't connect over host VPN

[GregKukanich]

I have a host Windows 10 system, my guest VM is CentOS 7. I have a VPN to connect to a remote server. When on the host and connected to the VPN I can connect and access the server. If I open a copy of my guest CentOS 7 VM migrated to virtual box with the VPN connected I am able to access the server from within the guest, but when using my guest CentOS 7 VM in Workstation Pro I cannot access the server, my internet works fine I can access any other site but I am not able to access the server. When I attempt too I get a 'DNS_PROBE_FINISHED_NXDOMAIN' error. I am not sure what the difference is between my VirtualBox setup and Workstation Pro, but both are set to NAT and one works but not the other. I have tried searching for answers and cant seem to find one that works.

[CarltonR]

With all that's occurred, may I suggest that you create a completely new, from scratch CentOS 7 VMware VM, if asked during the install use DHCP . . .  and test.

[GregKukanich]

Content from resolv.conf on VMware guest.

# Generated by NetworkManager
search localdomain
nameserver 8.8.8.8

Content from resolv.conf on VirtualBox guest.

#Generated by Network Manager
nameserver 10.0.2.3

I will attempt creating a new CentOS VM tomorrow and test it out. Thank you for the continued help!

[CarltonR · Accepted solution]

@GregKukanich wrote: Content from resolv.conf on VMware guest.

# Generated by NetworkManager
search localdomain
nameserver 8.8.8.8

the nameserver listed is Google's public DNS service . . . try changing to:

   nameserver 192.168.137.1
   nameserver 172.20.3.4
   nameserver 172.20.3.8

Note: don't forget to tab between 'nameserver' and the IP

[CarltonR]

If you have a VMware Guest Windows VM [NAT] setup on your host Win 10 system, then could you run 'ipconfig /all' and note what its DNS Servers IP is ?  Suspect it will be along the lines of 192.168.174.2, and then use this in the resolv.conf for the nameserver.

[GregKukanich]

This worked. Thank you so much! I had to put the '192.168.137.1' second otherwise I still couldn't connect to the remote server but now I am able to access both normal websites and the server.