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

3 NICS - VMWare Player - How do dedicate one NIC to host and the other two to Guest - Supernet?

This is my first attempt at virtualization:
Here is my plan.
I have two seperate physical networks.
The Host machine needs to be connected to one via its own seperate physical NIC.
The VMWare virtual machine needs to be connected to the other network via its own seperate physical NIC.
How do I designate one of the NICS in the host to be used by the host only.
How do I designate the other NIC to be used by the VM only with a different subnet?
The posts I've seen have screenshots of vmnetcfg.exe that are different from mine. I also cannot find and .cfg file listing all the network settings for Player.

FYI there will be one machine on the network that is unique from the others.
The virtual machine on that computer will need to have TWO seperate connections. One to EACH subnet... but be able to browse over both...
I have 3 NICS installed physically into the host machine..
The hosts will be on 192.168.0.x
The VM's will be on 196.168.1.x
This final machine with THREE NICS in it will have the host on 192.168.0.x and two connections on the VM...one to 192.168.1.x and the other to 192.168.0.x
The purpose of this is so that this one VM can access the VM network as well as one network device on the HOST network.
  • 3
  • 2
1 Solution
Paul SolovyovskyCommented:
-Connect each nic into a separate subnet, either a different vlan or switch.
-Create a VM network for each and assign the nics for the VM onto the nic for the subnet you want to be in.
-For the host define the ip address on this nic you want to use.  
-For VMs that need to be on multiple subnets add virtual nics and put them on the appropriate subnet.  Set them up as bridged and it should be in the broadcast domain that it was assigned to.

For better support I would recommend ESXi if your hardware supports it, it's an enterprise product that handles vlans and different subnets much better than vmware server.

JohnnyFiveAliveAuthor Commented:
So you're saying..
1. assign a different subnet to each NIC on the host.
2. Create a VMnet for the NIC I want to use in the VM
3. Assign the NIC i want to use in the VM to the VMnet

With a different subnet assigned to each of the NIC, I am running into a problem where XP stops communicating over the network.

Also, in the VM, the network connection in XP does not have an address even though I have assigned it to the VMnet and that VMnet is bridged to the appropriate NIC and that NIC has an IP

what am I missing here?
Paul SolovyovskyCommented:
In the VM you will need to assign the virtual nic an ip address that is bridged to the particular VMnet.  It may be a limitation in vvmware player, I normally use vmware workstation or ESX so I am not fully aware on vmware player limitations.
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

i have to ask, how do i create a virtual NIC so to speak to tie it to the 2nd physical one in my system?

under network adapter on my guest OS i have :  (using workstation 7)

Custom: Specific virtual network

and then it lists VMnet 0 - 9

0 being auto bridging and 1 being host only a  VMnet 8 says NAT
Paul SolovyovskyCommented:
Choose a physical nic and choose one of the VMnets that is not being used.
i went in under the virtual network editor in VMware 7 and i dont see any location that shows my realtek 2nd NIC card to assisn to anything? everything just says virtual this, virtual that?  I know i am missing something or am just not understanting this properly Sun's VM system you just select the NIC you want and your done.

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

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