Solved

vmware bridging/nat refuse to work with host teamed nics

Posted on 2013-01-31
11
1,057 Views
Last Modified: 2013-02-25
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.
0
Comment
Question by:MitchViste
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
  • 2
  • +1
11 Comments
 
LVL 30

Expert Comment

by:IanTh
ID: 38839992
so its a host yes ? you have to check the virtual networks setup correctly or is this workstation?/
0
 

Author Comment

by:MitchViste
ID: 38840063
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
 
LVL 121
ID: 38840154
The teaming software is unlikely to be compatible with the desktop hypervisor software.

Why not switch to Windows 2012 Hyper-V?
0
Instantly Create Instructional Tutorials

Contextual Guidance at the moment of need helps your employees adopt to new software or processes instantly. Boost knowledge retention and employee engagement step-by-step with one easy solution.

 

Author Comment

by:MitchViste
ID: 38840185
Because this is for home and I already have workstation. I also like vmware better.
0
 

Author Comment

by:MitchViste
ID: 38840206
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
 
LVL 121
ID: 38840222
I do not think, VMware Tools is going to make any difference to the networking functions.
0
 

Author Comment

by:MitchViste
ID: 38840312
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
 
LVL 121

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 38841093
low level networking issues with the Hypervisor networking.
0
 
LVL 16

Expert Comment

by:vivigatt
ID: 38843623
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
 

Author Comment

by:MitchViste
ID: 38844353
Everything works fine if I am using just the one NIC.
0
 
LVL 30

Expert Comment

by:IanTh
ID: 38844602
dont team them just connect both of them to the switch vmware will use both of them anyway
0

Featured Post

PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

HOW TO: Upload an ISO image to a VMware datastore for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere Host Client, and checking its MD5 checksum signature is correct.  It's a good idea to compare checksums, because many installat…
In this step by step tutorial with screenshots, we will show you HOW TO: Enable SSH Remote Access on a VMware vSphere Hypervisor 6.5 (ESXi 6.5). This is important if you need to enable SSH remote access for additional troubleshooting of the ESXi hos…
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …
Teach the user how to use create log bundles for vCenter Server or ESXi hosts Open vSphere Web Client: Generate vCenter Server and ESXi host log bundle:  Open vCenter Server Appliance Web Management interface and generate log bundle: Open vCenter Se…

624 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question