No guest internet access (bridged network on host with team NIC)

[Racekonijn]

Hi,

I'm using vmware player 3.1.1 on a windows 7 (64-bit) host machine with dual NIC.
My mobo is ASUS striker II extreme with Nvivdia nforce 790i ultra.

I have configured my machine to team up my NIC's to one. But since then i can't acces to the internet at my Virtual machines (guests).

My guest is configured to bridge and is having a ip adres from my dhcp server. (so far everything looks correct)

I can acces from the guest to my host, but not from my host to the guest and i can't access the internet from my guest.
My host is connected by two physical LAN cables.

I have tried in vmnetcfg to exclude the virtual team network adapter, but then i have no connection at all at my guest.
Also i can't choose to link one of my physical NIC's to VMnet0 beceause they are not showed by the virtual network editor when my host is configured as team NIC.
I can select my physical NIC when no team NIC is confgured.

But what i want is team up my host and my guests configured as bridge to acces the internet?
How can i manage that?

Below you can find my configs (ipconfig's in dutch).

My vmx file:
.encoding = "windows-1252"
config.version = "8"
virtualHW.version = "6"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
memsize = "756"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "Windows Vista.vmdk"
ide1:0.present = "TRUE"
ide1:0.fileName = "F:\Windows Vista (NL) 32Bit.iso"
ide1:0.deviceType = "cdrom-image"
floppy0.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.wakeOnPcktRcv = "FALSE"
usb.present = "TRUE"
ehci.present = "TRUE"
sound.present = "TRUE"
sound.fileName = "-1"
sound.autodetect = "TRUE"
svga.autodetect = "TRUE"
pciBridge0.present = "TRUE"
mks.keyboardFilter = "allow"
displayName = "Windows Vista NL (LeeCW)"
guestOS = "winvista"
nvram = "Windows Vista.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibility = "hosted"
tools.upgrade.policy = "useGlobal"

ide1:0.autodetect = "TRUE"
floppy0.fileName = "A:"
extendedConfigFile = "Windows Vista.vmxf"

ide1:0.startConnected = "TRUE"
ethernet0.addressType = "generated"
uuid.location = "56 4d 34 2b d6 37 94 bc-d1 72 90 83 f8 e9 5e 30"
uuid.bios = "56 4d a2 0c 7f f8 8b be-4c f7 de 6f 71 bf a4 a5"
scsi0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
scsi0.pciSlotNumber = "16"
ethernet0.pciSlotNumber = "32"
sound.pciSlotNumber = "33"
ehci.pciSlotNumber = "34"
ethernet0.generatedAddress = "00:0c:29:bf:a4:a5"
ethernet0.generatedAddressOffset = "0"
tools.syncTime = "TRUE"

checkpoint.vmState = ""

ethernet0.linkStatePropagation.enable = "FALSE"
usb.autoConnect.device0 = ""
vmotion.checkpointFBSize = "16777216"
ethernet0.connectionType = "bridged"
cleanShutdown = "FALSE"
replay.supported = "FALSE"
replay.filename = ""
debugStub.winOffsets.version = "7"
debugStub.winOffsets.value = "0xa0,0x9c,0x18,0x168,0x14c,16,376,0x248,0x240,0x210,0x1f8,0x84,0x28,0x18,0x20,0x24,1,0x240,0x0,0xc,0x14,0x200000,0x188,0xc,0xc,0x18,0x114,0x1cc"

Ipconfig from host

C:\>ipconfig /all

Windows IP-configuratie

   Hostnaam  . . . . . . . . . . . . : Racekonijn-PC
   Primair DNS-achtervoegsel . . . . :
   Knooppunttype . . . . . . . . . . : hybride
   IP-routering ingeschakeld . . . . : nee
   WINS-proxy ingeschakeld . . . . . : nee
   DNS-achtervoegselzoeklijst. . . . : geertdebaets.be

Ethernet-adapter voor LAN-verbinding 3:

   Verbindingsspec. DNS-achtervoegsel: geertdebaets.be
   Beschrijving. . . . . . . . . . . : NVIDIA nForce Networking Controller Virtu
al
   Fysiek adres. . . . . . . . . . . : 00-1F-C6-66-ED-AD
   DHCP ingeschakeld . . . . . . . . : ja
   Autom. configuratie ingeschakeld  : ja
   Link-local IPv6-adres . . . . . . : fe80::34ee:4ab5:88f5:8c8c%19(voorkeur)
   IPv4-adres. . . . . . . . . . . . : 10.0.0.3(voorkeur)
   Subnetmasker. . . . . . . . . . . : 255.255.255.0
   Lease verkregen . . . . . . . . . : maandag 2 mei 2011 18:07:25
   Lease verlopen. . . . . . . . . . : vrijdag 9 juni 2147 2:25:13
   Standaardgateway. . . . . . . . . : 10.0.0.1
   DHCP-server . . . . . . . . . . . : 10.0.0.1
   DHCPv6 IAID . . . . . . . . . . . : 436215750
   DHCPv6-client DUID. . . . . . . . : 00-01-00-01-14-C4-BB-93-00-1F-C6-66-ED-AD

   DNS-servers . . . . . . . . . . . : 195.130.131.133
                                       195.130.130.5
   NetBIOS via TCPIP . . . . . . . . : ingeschakeld

Ethernet-adapter voor VMware Network Adapter VMnet1:

   Verbindingsspec. DNS-achtervoegsel:
   Beschrijving. . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
1
   Fysiek adres. . . . . . . . . . . : 00-50-56-C0-00-01
   DHCP ingeschakeld . . . . . . . . : nee
   Autom. configuratie ingeschakeld  : ja
   IPv4-adres. . . . . . . . . . . . : 192.168.163.1(voorkeur)
   Subnetmasker. . . . . . . . . . . : 255.255.255.0
   Standaardgateway. . . . . . . . . :
   NetBIOS via TCPIP . . . . . . . . : ingeschakeld

Ethernet-adapter voor VMware Network Adapter VMnet8:

   Verbindingsspec. DNS-achtervoegsel:
   Beschrijving. . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
8
   Fysiek adres. . . . . . . . . . . : 00-50-56-C0-00-08
   DHCP ingeschakeld . . . . . . . . : ja
   Autom. configuratie ingeschakeld  : ja
   Automatisch geconf.IPv4-adres . . : 169.254.63.60(voorkeur)
   Subnetmasker. . . . . . . . . . . : 255.255.0.0
   Standaardgateway. . . . . . . . . :
   NetBIOS via TCPIP . . . . . . . . : ingeschakeld

Tunnel-adapter voor isatap.geertdebaets.be:

   Verbindingsspec. DNS-achtervoegsel: geertdebaets.be
   Beschrijving. . . . . . . . . . . : Microsoft ISATAP Adapter
   Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP ingeschakeld . . . . . . . . : nee
   Autom. configuratie ingeschakeld  : ja
   Link-local IPv6-adres . . . . . . : fe80::5efe:10.0.0.3%12(voorkeur)
   Standaardgateway. . . . . . . . . :
   DNS-servers . . . . . . . . . . . : 195.130.131.133
                                       195.130.130.5
   NetBIOS via TCPIP . . . . . . . . : uitgeschakeld

Tunnel-adapter voor LAN-verbinding*:

   Mediumstatus. . . . . . . . . . . : medium ontkoppeld
   Verbindingsspec. DNS-achtervoegsel:
   Beschrijving. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP ingeschakeld . . . . . . . . : nee
   Autom. configuratie ingeschakeld  : ja

Tunnel-adapter voor isatap.{C604F145-D2EC-4115-BDAD-336528A552E6}:

   Mediumstatus. . . . . . . . . . . : medium ontkoppeld
   Verbindingsspec. DNS-achtervoegsel:
   Beschrijving. . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP ingeschakeld . . . . . . . . : nee
   Autom. configuratie ingeschakeld  : ja

Tunnel-adapter voor isatap.{B6CC73F7-9E44-48F8-9198-209EB958CCD9}:

   Mediumstatus. . . . . . . . . . . : medium ontkoppeld
   Verbindingsspec. DNS-achtervoegsel:
   Beschrijving. . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP ingeschakeld . . . . . . . . : nee
   Autom. configuratie ingeschakeld  : ja

ipconfig from guest

C:\>ipconfig /all

Windows IP-configuratie

   Hostnaam  . . . . . . . . . . . . : LeeCW
   Primair DNS-achtervoegsel . . . . :
   Knooppunttype . . . . . . . . . . : hybride
   IP-routering ingeschakeld . . . . : nee
   WINS-proxy ingeschakeld . . . . . : nee
   DNS-achtervoegselzoeklijst. . . . : geertdebaets.be

Ethernet-adapter LAN-verbinding:

   Verbindingsspec. DNS-achtervoegsel: geertdebaets.be
   Beschrijving. . . . . . . . . . . : Intel(R) PRO/1000 MT-netwerkverbinding
   Fysiek adres. . . . . . . . . . . : 00-0C-29-BF-A4-A5
   DHCP ingeschakeld . . . . . . . . : ja
   Autom. configuratie ingeschakeld  : ja
   Link-local IPv6-adres . . . . . . : fe80::9416:7786:49c2:c0b2%9(voorkeur)
   IPv4-adres. . . . . . . . . . . . : 10.0.0.18(voorkeur)
   Subnetmasker. . . . . . . . . . . : 255.255.255.0
   Lease verkregen . . . . . . . . . : maandag 2 mei 2011 18:58:34
   Lease verlopen. . . . . . . . . . : vrijdag 9 juni 2147 2:26:14
   Standaardgateway. . . . . . . . . : 10.0.0.1
   DHCP-server . . . . . . . . . . . : 10.0.0.1
   DHCPv6 IAID . . . . . . . . . . . : 134220841
   DNS-servers . . . . . . . . . . . : 195.130.131.133
                                       195.130.130.5
   NetBIOS via TCPIP . . . . . . . . : ingeschakeld

Tunnel-adapter LAN-verbinding*:

   Mediumstatus. . . . . . . . . . . : medium ontkoppeld
   Verbindingsspec. DNS-achtervoegsel:
   Beschrijving. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Fysiek adres. . . . . . . . . . . : 02-00-54-55-4E-01
   DHCP ingeschakeld . . . . . . . . : nee
   Autom. configuratie ingeschakeld  : ja

Tunnel-adapter LAN-verbinding* 2:

   Verbindingsspec. DNS-achtervoegsel: geertdebaets.be
   Beschrijving. . . . . . . . . . . : Microsoft ISATAP Adapter
   Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP ingeschakeld . . . . . . . . : nee
   Autom. configuratie ingeschakeld  : ja
   Link-local IPv6-adres . . . . . . : fe80::5efe:10.0.0.18%14(voorkeur)
   Standaardgateway. . . . . . . . . :
   DNS-servers . . . . . . . . . . . : 195.130.131.133
                                       195.130.130.5
   NetBIOS via TCPIP . . . . . . . . : uitgeschakeld

Thans for any help!
I really appreciate any response.

Kind regards.

[Racekonijn]

Has no one any idea of this?

Any help would be great.

Thanks

[continuum]

have you disabled automatic bridging already ?

before you have not done that troubleshooting is moot

I just see that you use a Nvidia network-card ... not good.

Does this card still have the buildin firewall ? - if yes - disable that

[Racekonijn]

When I set the automatic bridging on or off it makes no difference.

I get a IP adres from my DHCP but can't acces the internet. (I've tried with serveral virtual machines)

Nvidia network card is on my mobo, sry ...

I can't find anything of a firewall on that, so i guess there isn't one.

Even if I don't team up my nic's (i get two Ip-adresses for my host, set up bridged network to the guest), everything is ok, so I think my network card is ok so far.

Thanks for your help so far.

[YLeduc1234]

Question 1: why do you want to team you NIC cards? don't know too many people connecting to the internet with bandwidth of more the 15 Mbps. So 1 100 Mbps card should be more than sufficient.

Question 2: Where are you connecting your cards? Unless the switch you are connecting to is also configured for teaming, weird behavior will occur.

Question 3: Have you tried running your setup with only one NIC card to see if it work.

Regards.

[Racekonijn]

1-I want to use my computer also as media server for my TV. If i don't team up my NIC's the connection is broken after serveral minutes. So I must team to get it work.

2 & 3 - I connect throug a switch wich is fine I suppose. When i don't team up, everything works fine. So if there anything wrong with my switch, I would noticed it before on other things.

My switch is a Dell PowerConnect 2816, if you know how to (re-)configure it the correct way, I will try it for sure. Every chance of fixing this issue, is a chance for me.

Thanks for your help!

[uy]

http://www.vmware.com/pdf/esx2_NIC_Teaming.pdf

This may help.

VMWare seems to have their own virtual teaming. But in your case you are already teaming NICs in host. VMware is very likely not intercepting that teaming in your host. You may have to leave your host unteamed and team it within VMWare.

Teaming is a diver virtualization of 2 physical NICs, VMware is yet another virtualization. Unless VMware intercept AFTER your teaming driver's level (which I doubt) it isn't going to work as you had expected. I suspect VMware intercepted your hardware BELOW your teaming driver, and go direct to see 2 physical NICs instead of your 1 virtual NIC.

However there is a chance.

I suggest you try to edit your virtual network using virtual network editor:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101869...

When you are at the editor don't bridge to any of the 2 physical NICs, but try to bridge to a logical virtualized NIC produced by your teaming driver. If you can see it appearing there inside Vmware's Virtual Network Editor, then your chance is very good. If you can only see 2 physical NICs (excluding the vmware's vment8(NAT) & vmnet1(HOST ONLY) then you have no chance.

[YLeduc1234]

Hello,

NIC teaming can be done on your 2816.  P 133 of the following guide will explain how. http://support.dell.com/support/edocs/network/pc28xx/en/ug/pdf/ug_en.pdf.

I am not quite sure of your setup but teaming does not mean double the speed. What normally happens is that based on the source and destination one specific NIC will be used. So if your PC is doing unicast to another specific device, only one NIC will be involved.

regards

[Racekonijn]

@uy

I'm understanding what you mean, VM ware makes a virtual team on it's own.

But if I don't team up my NICS on myself, I can't use my server/pc as media server (for my tv). So I need to team up.

What I've tried for you:

I've tried to configure as follow (via vmnetcfg.exe beceause I'm using vmplayer, not vm workstation):

on the tab Automatic Bridging I switched off 'Automatic choose an available physical network adapter to bridge to VMnet0'

on the tab Host Virtual Network Mapping I linked VMnet0 to 'NVIDIA nForce Networking Controller Virtual'

All the other settings i let unchanged.

I think this configuration should do it for me? no?

The same result so far, I'm getting a ip adres from my DHCP server, but can't acces the internet from my guests.

What I also tried is this:

on the tab Automatic Bridging I switched on  'Automatic choose an available physical network adapter to bridge to VMnet0'

and try to add my phisical nics to the exclude-list, but they didn't appear. I only can choose the 'NVIDIA nForce Networking Controller Virtual' (which is the only currently active NIC)

If you think I'm doing something wrong at the configuration, please tell me, I will try every suggestion.

Thanks for your help so far.

[Racekonijn]

@YLeduc1234

The reason for my team up NICS, is not directly to increase the speed, but to make my media streaming work. If I don't team up, I loose my connection after some minutes to my server (which is really anoying if you try to watch a movie)

I don't know if I need to change the settings of my switch here, I doubt it, but it's possible. I want to try some things for you if you want. But i'm not an expert of switch configuration. (I will play somewhat with the LAG of my switch, if it brings a solution I let you know for sure)

Thanks for your help so far.

Really appreciated.