So I turned on my test SBS 2011 server today to test out the latest Exchange Update Rollup and was greeted by an VM that was hanging on startup. Looking into the issue more closely the virtual network adapter was disconnected and when I tried to select ‘connect’ I received the following error message:
The network bridge on device ‘VMnet0’ is not running. The virtual machine will not be able to communicate with the host or with other machines on your network. Failed to connect virtual device ‘Ethernet0’.
I’m updating my certifiactions at the moment and to help with my VCP I’m in the process of building a vSphere 6 home lab. I’m using VMware workstation and within it I’m setting up two ESXi 6.0 hosts, a vCSA and a single DC. Each ESXi host has ten NICs with will be distributed and teamed onto five different networks, Management, Storage, vMotion, and two sudo VLANs for VMs. The problem is only the first Network Adpater which was bridged has been detected correctly.
At first i didn’t notice it, as in VM Workstation everything looks ok. The Network Adapters were added in VMware Workstation with out an issue, and assigned to the correct custom virtial networks. Continue reading