Could someone please explain how networking works with the player?

[boeckelr]

Hi - could someone please explain how networking works with the player?

In other words, what exactly do VMnet1 and VMnet8 do and how do they work? I know they are virtual NICS created by the Player...but does VMNET1 correspond to eth0 and VMnet8 to eth1? or something different?

Or if there is a document somewhere that has this info, if you could please point me in that direction, that would be great!

I have looked in the Players docs, but couldnt find what I was looking for....and tried in the KB but couldnt really find it there either.

What I need is this: I have 2 NICS in my PC, and 2 VLANS on my network....and while running the player would like to assign eth0 to VLAN1 and eth1 to VLAN2....how do I do this? Sorry if this is a basic question.

Thanks!

Mike

Message was edited by:

boeckelr

Message was edited by:

boeckelr

[RDPetruska]

You can read the appropriate section of the Workstation manual on networking, as Player is basically much the same codebase as Workstation.

In a nutshell:

The VMnet1 adapter is used for "host-only" networking - between guest and host only, no outside LAN.

The VMnet8 adapter is used for "NAT" networking - guest can see outside but is hidden from the LAN, with the exception of specifically mapped ports the user must configure.

Bridged mode allows your guest its own IP on the LAN, and makes it look like just another PC on the network.

In your case, you need to have 2 virtual NICs in your guest. And, you need to run the virtual network editor (or the network configuration script if you're on a Linux host), disable automatic bridging, and specify each of your host's physical NICs to bridge to a different VMnet switch (use any of the unused ones - 2-7, 9). Then set your VM's NICs to use custom network connection, and specify which VMnet each should connect to.

[boeckelr]

Thanks!

Exactly what I needed....one more question though - the virtual network editor - is that available with the Player? or just with Workstation? Or is it with the tools?

Thanks again.

[RDPetruska]

vmnetcfg.exe, located in the Player installation folder. Workstation and Server create a shortcut for it, but Player doesn't.

[boeckelr]

Thank you!

[boeckelr]

Hi - a few weeks ago I asked about how networking works in Vmware Player/Workstation.

I want to run two VM's, and need each to access one of my two lans. I will probably do this with Player but maybe w/Workstation in the future. So VM1 will need to be on on LAN1 and VM2 will need to be on LAN2 obviously.

So how exactly do I do this? I have 2 NICs on my PC.

I know that I need to run the Virtual Network Editor....and then disable automatic bridging....but then what? I assume I need to use bridging between each of my 2 NICs.

Do I need to goto the "Host Virtual Adapter" tab and add 2 new virtual adapters? say VMnet4 and VMnet5? But after that how do I assign which virtual adapter each VM uses? Is this something that I need Workstation for? or can I choose this in Player?

I have played around with Workstation 6 beta for several days now and I still cant figure out this networking...and the thing is I am not computer illiterate. It just doesnt seem to be working the way I think it should - because if I dont create a new virtual adapter, and instead just select my NIC's for VMNet4 and VMNet5, then things dont work....but is this the way I should be doing it???

And what does VMNet0 do? Is that reserved for automatic bridging only? Or something else?

I really like this software...plan to buy it soon, I can see so many new ways to do things using it.

Thanks in advance for your help.

Message was edited by:

boeckelr

[RDPetruska]

On the 2nd tab in the Network Editor, just use the combo boxes to specify which physical NIC you want to bridge to which VMnet - you can use VMnet0 for one of them (and keep your guest(s) you want using that NIC set to bridged), and use one of the other unused VMnets (2-7, 9) for the other NIC. For those guests, you need to change to Custom connection, and specify the VMnet # which you bridged the 2nd NIC to.