• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5603
  • Last Modified:

Can't bridge multiple network adapters in VMWare Server 2.0

I installed VMWare Server 2.0 on a Windows 2003 Server (Standard Edition).  The host also has two network cards, one connected to a network and the other connected to a network.  I created the guest VM using the VMWare Conversion utility on a second physical machine.  The guest VM starts fine, but I can not get the two NIC's to bridge so that the guest OS can access both networks at the same time.

I have set up the guest network adapters as bridged and have tried every way I can imagine of configuring the virtual network adapters from within the Virtual Network Manager utility (making sure to refresh the network every time I make a change).  For example, I have tried bridging vmnet0 to the one network card and then vmnet2 to the other.  I have tried doing the same with vmnet2 and vmnet3.  I have switched the properties of each virtual adapter within the guest.

Right now, I have vmnet0 and vmnet2 configured.  However, whatever host network card is bound to vmnet0 seems to be the only network that works for the guest; I can get it to see each network by doing that, but never both at the same time.  Both guest NIC's say that they're connected.  In testing, I also set each to obtain IP addresses from the DHCP server, and both NIC's on the guest OS obtain IP addresses from the same network (again, whichever one is bound to vmnet0).
1 Solution
I would recoment disableling the automatic bridging.
This can be done in the "manage virtual network editor"
Under the tab "Automatic bridging"
Once you have done this, then go to the "Host Virtual Network Mapping" Tab and config the VMnics with the host network card.

I hope it helps.
RAHopkinsonAuthor Commented:
I have alrady disabled the Automatic Bridging feature.  On the Host Virtual Network Mapping tab, I have configured the NIC's on vmnet0 & 2 and vmnet 2 & 3, but the guest OS only sees what's on vmnet0.

You need to click on your Host (vmware server host) and click 'Refresh Network List'.  Your bridged network should now appear in the 'Networks' list and will then be selectable when you setup your network adapters for your vm's.

RAHopkinsonAuthor Commented:
In the original question, you'll see the phrase "making sure to refresh the network every time I make a change," so that wasn't the issue (although it took me a while at first to find that option).

The problem turned out to be one of nomenclature.  In the guest virtual adapter settings, I took "bridged" to mean the type of network connection--not the actual interface.  In VMWare 2.0, "bridged" means "vmnet0" so setting the guest network adapters to "bridged" and "vmnet2" respectively solved the problem.
I am having the same problem, but I don't seem to understand how you solved it.  I got to the point you did in the Accepted Solution, but I am not clear what steps you took to solve.  What are your settings in the "Host Virtual Network Mapping" tool and also in the VMWare web console for the guest settings?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now