Cannot connect to guest, but host has can access internet
I upgraded lately to Workstation 16 and I have huge problems with connectivity and I am already kind of frutrated from the issue.
The problem: I have ubuntu 20.04 runnig the latest Vmware tools and the newest version of Workstation. Guest can ping host (192.168.67.2) and it can access internet through NAT network adapter but host cannot access guest at all - no ping reply or TCP connection possible.
I am running in Ring level 3 along with Docker. Neweset Windows update. No special firewall rules in Linux, I can also cannot see any packets coming in when running tcpdump -i any -n
UPDATE 1:I cannot also ping from the Windows host system the guests default gateway (192.168.67.2).
12/09 UPDATE 2: I reinstalled Vmware Workstation and it was working 1 day. After reboot not working again
12/15 UPDATE 3:I tried to change the NAT network to 192.168.68.128. No effect. Created completely new VM, fresh install of Ubuntu, not working. VMs can ping themselves between each other though.
12/16 UPDATE 4: I will reinstall now again, and keep you updated.
Was this running prior to upgrading to Workstation 16, and if so, what version was being used?
Has the version of Ubuntu changed?
With simple NAT interface, the host will only be able to reach the guest if the host has a route to the NAT'd subnet. Do a "netstat -r" command in the host. See example below. In the purple/pink area, if you don't see a destination to your NAT subnet, that answers why your host can't reach the guest. If we determine this is the fundamental reason for the disconnect, we can later try to find-out why that route is not getting installed in your host routing table. If the route exists and points to the proper pseudo-interface, then we must debug why the packets aren't getting there.
I am facing the same situation: Windows 10 Enterprise, 64-bit (Build 19043.1348) 10.0.19043 VMware Workstation Pro 16.2.1 build 18811642
VM can reach internet and it is configured to use NAT Host can reach internet VM cannot ping host and vice versa nor I can connect from either direction
In my preliminary investigation virtual network created for NAT was bound to VMware Network Adapter VMnet8.
ipconfig showed that vmnet8 had an ip allocated from the class 169 which somehow proved that the NIC is not getting an IP from DHCP service created by vmware for this virtual network.
Steps to fix it: - I tried to manually add an IP to VMnet8 from this subnet (.3) -> Failed - disabled completely windows firewall AND VM iptables
What worked: - I have opened Virtual Network Editor, - I unchecked "Connect a host virtual adapter to this network" and Applied - Checked it back and Applied
After that ipconfig was showing an IP from that subnet and I was able to reach the VM