Its a problem of Fusion in combination with Big Sur (due to Apple dropping support for kernel extensions, VMware had to find other means to establish virtual networks - and Apple left only very few limited options).
From my standpoint the simplest workaround is just to ignore DHCP and configure IP manually. So for example if your subnet for the VM is 192.168.77.0/24, configure something like 192.168.77.20 as the IP for your guest and use 255.255.255.0 (or 24) as subnet mask (or prefix length) and usually 192.168.77.1 as gateway/router and also for DNS and maybe WINS. If your OS requires an explicit broadcast address, use 192.168.77.255 (for the mentioned sample subnet). That's about it.
When you have multiple VMs that should be able to talk to each other, manually assign them IPs like above, but avoid the IPs .0, .1, .2, and .255.
Be aware not to simple use the numbers mentioned here! Adapt the subnet 192.168.77.0 to your needs and current configuration of Fusion! Sadly, the Fusion UI hides all of these details. So have a look at the file /Library/Preferences/VMware\ Fusion/networking and use the value set for VNET_8_HOSTONLY_SUBNET. Or start your VM and inspect the IP configuration set (even if DNS resolution does not work, the basic configuration at least of the subnet will be correct).
I have the Problem with Bridged after coming back from sleep Mode of my Mac Book.
All VM have no Network(Internet, LAN)
I have to restart the complete VMWare Fusion 12 then the VM reconnect.
Did your Windows 10 VM get other network information correctly? say, what's the IP address of the VM. Could you please help to upload the nat.conf resides in /Library/Preferences/VMware Fusion/vmnet8/nat.conf and vmware.log in the VM bundle? You can get vmware.log through below steps:
1.Right click the VM name on VM window
2.Click the path next to the VM name(location where VM resides) in the menu item list.
3.Right click the VM name in Finder and select 'Show Package Contents'
4.Navigate to vmware.log and upload it 🙂
And then please try the following steps and check if the network could work:
1.Shutdown the Windows 10 VM.
3.Re-launch Fusion and start up the Windows 10 VM
Same issue when using Internet Sharing network adapter on BigSur with Fusion 12.0.0.
Noticed that the default gateway has changed from .2 to .1
Seem to have a workaround - created a new custom network with the same subnet as used with Internet Sharing. Switched all VMs to use that custom network, and they seem to work out of the box with DHCP.
Need static IP's for my use case so have assigned those for all VM's.
Yes, there are a few differences on Big Sur host. 'X.X.X.1' will be used as the default gateway and dns for NAT VMs. But the default NAT network should work after upgrading if they were set to use DHCP(by using .1 as default gateway and dns).
My workaround for setting static IP config is only a rough sketch and not really complete. 🙂
The correct (NAT) gateway address (that should also provide DNS) can be found in /Library/Preferences/VMware\ Fusion/vmnet8/nat.conf. Near the top of the file you should find some lines like this:
# NAT gateway address ip = 192.168.xxx.y
This ip should be used inside the guest as the gateway address (and as DNS server). Next step would be to check, whether basic IP connectivity is given. Try these commands:
ping <gateway-ip> ping <other ip in your LAN> ping 18.104.22.168
So in your case try something like "ping 192.168.206.1". If all pings succeed and no errors occur, the basic network connectivity is OK. The next step would be to test DNS. For this try something like "nslookup ietf.org". If pings are OK and nslookup fails, DNS settings needs to be adjusted. You may use your Internet providers DNS server, your own local DNS server from your LAN or as a kind of last resort some other public DNS server (like 22.214.171.124; be aware that a public DNS provider sees *ALL* your connection destinations, e.g. they know all website servers you are visiting).
Hope, this helps a bit.
It seems, if you have manually adjusted something for the network settings (like manually selected subnet, configured some static IPs for DHCP etc.), the upgrade cannot handle this. In my case, after upgrading to Big Sur and then doing the upgrade from Fusion 11 to 12, the NAT server moved from .2 to .1 but DHCP still announces .2 as DNS server (but the gateway was correct). And I found no way to fix the erroneous DHCP announcements (so my only solution has been to fall back to static IP config, giving up on DHCP).
Hi @snobis ,
I set the VM to automatically get network information. I noticed it got the IP address 192.168.206.5 and gateway 192.168.206.1 which seems correct.
However, when pinging the gateway it still says request timed out so it doesn't even work locally without DNS...
@nancyz to be clear about my situation: I installed VMware Fusion 12 for the first time, I haven't used 11 or any other version so for me there wasn't any upgrade at all.
I've attached another screenshot.
If you have a new, fresh installation of Fusion there should be no problem with DHCP.
I think you have some other networking problem. Maybe any kind of firewalls that are wrongly configured (Windows Firewall inside the guest, MacOS Firewall (though the default configuration should be fine) and/or some other host firewall like Little Snitch). When I debug networking problems, my first step is to stop any other activities (mainly due to security concerns) and deactivate any kind of firewalls. Another tool that might be helpful is tcpdump or wireshark - but if you do not know these tools I'm afraid you have not much background in networking and they might overwhelm you. Oh, and after debugging the problem, do not forget to activate any security measures you deactivated (turning on all firewalls etc.), before resuming normal activities. 🙂
Sorry, if this is not too helpful. Maybe someone else has a bit more time and resources to help or maybe you find someone with more detailed networking knowledge among your friends/colleagues.
For anybody experiencing DNS-level problems in a VM using a NAT adapter (that is, IP-level stuff is fine, but no name will resolve via DNS), I've posted a workaround in https://communities.vmware.com/t5/VMware-Fusion-Discussions/DNS-Forwarder-Does-Not-Seem-to-Exist-in-...
Due to network-level changes in how VMware Fusion operates on Big Sur, it is now necessary to ensure that nothing is listening on port 53 on your host, regardless of scope. Either that or just configure each guest VM with a manual address for a DNS server, rather than have it use what DHCP says it should.
I have exactly the same problem!!!! OpenVPN network works in Big Sur but not in Linux/Windows Virtual Machine over NAT, the traffic routed form the Virtual Machine to the VPN network does not work since I upgraded to BigSure.
The problem is with Apple(macOS) Fusion12(VMware) or Cisco AnyConnect VPN(Cisco) ?
I tested with my personal MacBook Pro at home. Running macOS Big Sur without any VPN clients. Loaded Windows 10 VM with Fusion12 NAT works without problem..
At work I have same setup except my host macOS Big Sur has Cisco AnyConnect.. but NAT is not working...
@om3rx Some VPN configurations prevent any other network communications, which may even interfere with VMs being able to communicate. But that depends on the VPN.
If you want to test whether your connectivity problems lie on the IP layer or name resolution layer, you can try a few steps from a guest VM:
This should return something like:
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
The document has moved
If you got through step 4, congratulations. Everything is working fine.
If step 3 was the first to fail, then I suspect that you have the DNS-layer problem described elsewhere. This is VMware's fault.
If step 2 was the first to fail, then you have some IP-layer trouble. Specifically, your network isn't allowing outbound DNS requests. This could be because of how AnyConnect is configured.
If step 1 was the first to fail, then you have IP-layer trouble. Specifically, your network isn't allowing outbound web requests. This could be because of how AnyConnect is configured.
I am having similar issue with macOS Big Sur, Fusion 12 NAT connection and Cisco VPN, following this thread for a solution. Let me know if I can contribute by providing more info/ testing anything.