This error message occurs sometimes in VMWare Fusion on the Mac when using a certain networking setting. This setting, in particular, is the “bridge” function. “Bridge”, as opposed to “NAT”, means the Virtual Machine gets its own IP-address on your local area network. The “NAT” (Network Address Translation) option, however, makes your Mac act like a router behind which the VM resides. This makes the VM inaccessible to the outside LAN, but it still has access to the outer LAN or Internet.
Bridging for VMs is nice because this is a way you can set up a VM to act as a server – serving printers, web resources, media and files. But sometimes, VMWare Fusion behaves awry, throwing up the dreaded exception:
“The network bridge on device /dev/vmnet0 is not running”
This will cause the VM to be disconnected from the network. There’s no real indication what causes this. Neither does it allude to how to fix it. “Just a Blog” provides a solution:
- Close the ailing VM
- Open the “Terminal” from Applications/Utilities
- Type:
cd /Library/Application\ Support/VMWare\ Fusion/ - Type:
sudo boot.sh –restart - You may get a message warning you of the perils of sudo. Proceed.
- Re-open the VM and make sure network bridging is re-enabled through the Fusion’s “Settings” interface.
You should now be able to access the network through the respective VM. It may occur that this error crops up again. It seems to me that it happens arbitrarily. I wonder why Fusion can’t execute this command by itself, either.
I hope this helped 
.
