I've had a hell of time today trying to figure out vmware server 2 network bridging problem. The server I've setup more than 2 years ago have been running flawlessly with more than a few reboots over the course of 2 years, and never had network problem in the Guest Operating system running Centos 5.
Today, the data center I've been using have had power failure, and the server went down for an hour. After a reboot, the bridged network guest operating systems use suddenly stopped working. There were no changes to a vmware configuration, nor server setting as it was working just fine.
The Host server is running Windows 2003 SP2, 32-bit OS, and guests are all Centos 5. After some research, I found the following:
1. According to VMware administrative control panel, bridging is provided by vmnet0 as shown on GUI below.
2. The Network Connections show vmnet1 and vmnet8, but not vmnet0. I was expecting to see vmnet0 network connection, but it's not there.
VMnet0 never displays as a Virtual Network Adapter like NAT (VMnet8) or Host-only (VMnet1) Network Adapters because it's not a Network Adapter, it's a Protocol and will appear in the Host's Physical Network Adapter's Properties as VMware Bridge Protocol.
3. So, looking at the Local Area Network Connection, the VMware Bridge Protocol is enabled on both Local Area Network Connections.
I have 2 network adapters, one for public network and the other for private network. The bridging should be done on the public adapter. Looking at the LAN properties, I've found that the two adapters have both VMware Bridge Protocol turned on. This led me to believe that the network is confused which adapter to use when bridging to the public network. By unchecking VMware Bridge Protocol on Local Area Connection 2, I was able to resolve the problem.
Comments
Add new comment