vmware bridging/nat refuse to work with host teamed nics

I have a EVGA 122-CK-NF68-A1 LGA 775 NVIDIA nForce 680i SLI  motherboard:
http://www.newegg.com/Product/Product.aspx?Item=N82E16813188013

This mother board has drivers that allowed teaming (yes they are older now, but the new drivers disable the teaming function so I kept the older one. I have no trouble with the teaming at all except when I am trying to use this pc as a vmware host.

WhenI set up vmware player or workstation in either bridged or nat mode on this pc the guest OS (Linux) can only ping the host and cannot ping the router/network computers or the internet, even though it pulls a dhcp address in bridged mode which I would assume comes from the router since it's the same subnet.

I have used the network editor to choose the nvidia virtual adapter that was created during installation of vmware workstation.

It did work for a few minutes during one of the 30 times I reconfigured or started from scratch, but then wouldn't work again.

Does anyone know what I can do to get this working? I really don't want to get rid of the teaming as it gives my PC a 2Gbps connection to my network which is needed as this PC serves out all of my multimedia files to the network.
MitchVisteAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
low level networking issues with the Hypervisor networking.
0
 
IanThCommented:
so its a host yes ? you have to check the virtual networks setup correctly or is this workstation?/
0
 
MitchVisteAuthor Commented:
The host has teamed nics. The guest os does not. The host OS works fine. The guest, which is running on vmware workstation 9.01, OS does not.

The virtual network setup is correct as far as I can tell.

The host nice team has IP -  192.168.68.3

The guest OS pulls a dhcp address from the router (I assume) of 192.168.68.100 or beyond as that is where my dhcp range starts.

When natted the guest OS pulls a 192.168.x.x range.

No firewalls running on either the host or the guest OS at this point.
0
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The teaming software is unlikely to be compatible with the desktop hypervisor software.

Why not switch to Windows 2012 Hyper-V?
0
 
MitchVisteAuthor Commented:
Because this is for home and I already have workstation. I also like vmware better.
0
 
MitchVisteAuthor Commented:
Would vmware tools make a difference in networking? I believe I have an outdated version per a warning on boot of the guest os
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I do not think, VMware Tools is going to make any difference to the networking functions.
0
 
MitchVisteAuthor Commented:
What stumps me is that the guest OS will contact the router via DHCP, pull an address, and even be listed as a dhcp client on the router, yet I cannot ping it or get internet access. frustrating!
0
 
vivigattCommented:
Can you "un-team" the host NIC(s) and check that everything is working as expected?

If so, I would suspect an implementation issue causing bad interactions with the host nic. A team may be considered a bridge, which is also what VMWare WS/Player will use to provide network access to the guests, then creating somewhat a bridge on a bridge, which may be tricky and my not have been completely validated/tested/supported
0
 
MitchVisteAuthor Commented:
Everything works fine if I am using just the one NIC.
0
 
IanThCommented:
dont team them just connect both of them to the switch vmware will use both of them anyway
0
All Courses

From novice to tech pro — start learning today.