Fusion created 'vmnet' interfaces and managed them itself. Here's what I found:įusion 11 on Catalina managed the NAT. I used Fusion 11 on Catalina and upgraded to Fusion 12 on Big Sur. Parallels really is starting to sound better by the day.

This issue exists with common configurations and can be easily reproduced with that said, VMware really needs to address this and soon. We should probably make a separate thread specifically for this issue that's not caused by excessive OS tweaking or bonkers VPN clients that jack up the network stack. As noted in my previous comment, the issue doesn't appear to affect Linux guests (Ubuntu in this case), based on that it leads me to believe something within the guest needs to be reconfigured, perhaps a VMware tools update is needed to resolve this issue after changes to Windows over time via patching, etc. can be reproduced easily on a fresh install of Fusion and in a fresh Windows 10 guest. If you look at the title of the thread you'll see it's technically about NAT no internet connection, not bridged no internet connection. These 'fixes' will not work for our problem. Exactly the same problem as Many are toting fixes that resolve issues that exist after previously modifying their network configuration at a system level, or using (certain?) VPN clients on the host while running guest VMs that may have done so for them (why not just run the VPN in the guest?).

Globalprotect vpn big sur