Solved: Windows 7 (x64) NIC connection problems (IPv4)

am1367 · ‎09-22-2010

Hi everybody,

the technical details first:

- Host-PC-OS: Windows 7 x64

- VMWare Workstation V. 7.1.1

- Guest OS: 1 x Windows XP Prof, 1 x Windows 7 x64 (for software test purposes)

both guests are configured with an individual IP (v4): 192.168.1.X / Subnet mask 255.255.255.0 - that means DHCP:no, Network

connection in VMWare: Bridged

My problem is as follows:

The XP guest is set to a briged network mode and communicates pretty fine with the network via the "VMWare Accelerated AMD Adapter". I get access to the network itself as well as to the internet.

The Windows 7 guest gets no access to the network via the "Intel(R) PRO/1000 MT" driver. When I analyse the connection details I find that there are 2 different IPv4 adresses listed:

Automatically configured IPv4 adress 169.254.202.162

IPv4 subnet mask 255.255.0.0

Automatically configures IPv4 adress 192.168.1.x

IPv4 subnet mask 255.255.255.0

I know that the upper IP adress is generated by windows itself - due to no network connection. But why does Windows 7 doesn't get this connection. The XP guest works fine with the same settings. I even tried a NAT connection - that eliminated the upper IP but I hadn't any Internet connection either :-(...

Any suggestions?

Thx for your help in advance!

Alex

AWo · ‎09-23-2010

First of all, you should be able to access the NAS shares via the NAT connection.

Second, what do you mean by bridge 2 IP ranges? If you have only one physical IP subnet you can't bridge two different IP ranges to that network. In fact, if you use bridge you do not bridge an IP subnet at all. Bridging means that the virtual NIC gets transparently connected to the physical network. That means you must use the physical network IP addressing scheme in the guest then.

When you use NAT, you connect the guest to a virtual switch/network (called VMnet8) which has its own IP subnet range. That's the reason why the VMnet8 (NAT) IP network address must be different from the physical one (which was not the case in the beginning). The host does the NAT work and routes the packets to the physical network then.

So, as long as your host does not have two NIC's each connected to different IP subnets, there's no need to create two bridges.

Have you tried the bridge again? Remember, do not use automatic bridging, disable IPv6 and disable all firewalls while testing. Set the host connections to "private" or "home".

AWo

VCP 3 & 4

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

View solution in original post

AWo · ‎09-22-2010

Welcome to the forums!

The Windows 7 guest gets no access to the network via the "Intel(R) PRO/1000 MT" driver. When I analyse the connection details I find that there are 2 different IPv4 adresses listed: Automatically configured IPv4 adress 169.254.202.162
IPv4 subnet mask 255.255.0.0
Automatically configures IPv4 adress 192.168.1.x
IPv4 subnet mask 255.255.255.0

Are both listed on the same single adapter? Or do you have two network cards in that single guest?

Post "ipconfig /all" from host and guest! No need to worry as you use private IP addresses.

I know that the upper IP adress is generated by windows itself - due to no network connection.

Yes, the APIPA address is issued when an adapter configured for DHCP doesn't receive an address. SO if that adapter faces the bridged connection and there is no DHCP server you get this address until you eneter a static IP address.

AWo

VCP 3 & 4

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

am1367 · ‎09-22-2010

Both guests are listet on the same adapter because the host only have one installed (FRITZ! Wlan adapter). Bridging mode in the Virtual Network Editor ist set to "Automatic" - but that doesn't affect anything since only the WLan adapter is present/connected ....

OK .. this is the ipconfig of the host:

-

Microsoft Windows http://Version 6.1.7600

Windows-IP-Konfiguration

Hostname . . . . . . . . . . . . : IV-WST1AM-DE

Primäres DNS-Suffix . . . . . . . :

Knotentyp . . . . . . . . . . . . : Hybrid

IP-Routing aktiviert . . . . . . : Nein

WINS-Proxy aktiviert . . . . . . : Nein

Drahtlos-LAN-Adapter Drahtlosnetzwerkverbindung 2:

Verbindungsspezifisches DNS-Suffix:

Beschreibung. . . . . . . . . . . : FRITZ!WLAN USB Stick N

Physikalische Adresse . . . . . . : 00-1C-4A-FC-28-D8

DHCP aktiviert. . . . . . . . . . : Nein

Autokonfiguration aktiviert . . . : Ja

Verbindungslokale IPv6-Adresse . : fe80::5d8b:84c0:8f2b:b554%14(Bevorzugt)

IPv4-Adresse . . . . . . . . . . : 192.168.1.16(Bevorzugt)

Subnetzmaske . . . . . . . . . . : 255.255.255.0

Standardgateway . . . . . . . . . : 192.168.1.200

DHCPv6-IAID . . . . . . . . . . . : 436214858

DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-12-D8-AF-44-00-1F-3F-05-34-5D

DNS-Server . . . . . . . . . . . : 192.168.1.200

NetBIOS über TCP/IP . . . . . . . : Aktiviert

Ethernet-Adapter VMware Network Adapter VMnet1:

Verbindungsspezifisches DNS-Suffix:

Beschreibung. . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet

1

Physikalische Adresse . . . . . . : 00-50-56-C0-00-01

DHCP aktiviert. . . . . . . . . . : Nein

Autokonfiguration aktiviert . . . : Ja

Verbindungslokale IPv6-Adresse . : fe80::b55d:c561:6c71:61e3%16(Bevorzugt)

IPv4-Adresse . . . . . . . . . . : 192.168.211.1(Bevorzugt)

Subnetzmaske . . . . . . . . . . : 255.255.255.0

Standardgateway . . . . . . . . . :

DHCPv6-IAID . . . . . . . . . . . : 268456022

DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-12-D8-AF-44-00-1F-3F-05-34-5D

DNS-Server . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS über TCP/IP . . . . . . . : Aktiviert

Ethernet-Adapter VMware Network Adapter VMnet8:

Verbindungsspezifisches DNS-Suffix:

Beschreibung. . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet

8

Physikalische Adresse . . . . . . : 00-50-56-C0-00-08

DHCP aktiviert. . . . . . . . . . : Nein

Autokonfiguration aktiviert . . . : Ja

Verbindungslokale IPv6-Adresse . : fe80::34cc:bd8:43a0:60bc%18(Bevorzugt)

IPv4-Adresse . . . . . . . . . . : 192.168.1.1(Bevorzugt)

Subnetzmaske . . . . . . . . . . : 255.255.255.0

Standardgateway . . . . . . . . . :

DHCPv6-IAID . . . . . . . . . . . : 302010454

DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-12-D8-AF-44-00-1F-3F-05-34-5D

DNS-Server . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS über TCP/IP . . . . . . . : Aktiviert

Tunneladapter isatap.{793170D4-9020-49AD-A0F2-C80F046AB42C}:

Medienstatus. . . . . . . . . . . : Medium getrennt

Verbindungsspezifisches DNS-Suffix:

Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter

Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0

DHCP aktiviert. . . . . . . . . . : Nein

Autokonfiguration aktiviert . . . : Ja

Tunneladapter isatap.{CC1A7C3B-2C59-4F57-BAFA-109660607140}:

Medienstatus. . . . . . . . . . . : Medium getrennt

Verbindungsspezifisches DNS-Suffix:

Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #2

Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0

DHCP aktiviert. . . . . . . . . . : Nein

Autokonfiguration aktiviert . . . : Ja

Tunneladapter isatap.{95627D26-326C-48FC-91E0-465D75647A6A}:

Medienstatus. . . . . . . . . . . : Medium getrennt

Verbindungsspezifisches DNS-Suffix:

Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #3

Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0

DHCP aktiviert. . . . . . . . . . : Nein

Autokonfiguration aktiviert . . . : Ja

Tunneladapter Teredo Tunneling Pseudo-Interface:

Verbindungsspezifisches DNS-Suffix:

Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0

DHCP aktiviert. . . . . . . . . . : Nein

Autokonfiguration aktiviert . . . : Ja

IPv6-Adresse. . . . . . . . . . . : 2001:0:5ef5:79fd:34f3:1c23:3f57:feef(Bevo

rzugt)

Verbindungslokale IPv6-Adresse . : fe80::34f3:1c23:3f57:feef%15(Bevorzugt)

Standardgateway . . . . . . . . . : ::

NetBIOS über TCP/IP . . . . . . . : Deaktiviert

-

And here comes the ipconfig of the guest - which has already an assigned fix IP adress .. so as far as I unstand no DHCP server is needed...

-

Windows-IP-Konfiguration

Hostname . . . . . . . . . . . . : WIN7_x64

Primäres DNS-Suffix . . . . . . . :

Knotentyp . . . . . . . . . . . . : Hybrid

IP-Routing aktiviert . . . . . . : Nein

WINS-Proxy aktiviert . . . . . . : Nein

Ethernet-Adapter LAN-Verbindung:

Verbindungsspezifisches DNS-Suffix:

Beschreibung. . . . . . . . . . . : Intel(R) PRO/1000 MT-Netzwerkverbindung

Physikalische Adresse . . . . . . : 00-0C-29-4F-5E-36

DHCP aktiviert. . . . . . . . . . : Nein

Autokonfiguration aktiviert . . . : Ja

Verbindungslokale IPv6-Adresse . : fe80::bd22:f632:2f1d:1194%13(Bevorzugt)

IPv4-Adresse (Auto. Konfiguration): 169.254.202.162(Dupliziert)

Subnetzmaske . . . . . . . . . . : 255.255.0.0

IPv4-Adresse . . . . . . . . . . : 192.168.1.27(Dupliziert)

Subnetzmaske . . . . . . . . . . : 255.255.255.0

Standardgateway . . . . . . . . . : 192.168.1.200

DHCPv6-IAID . . . . . . . . . . . : 268438569

DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-14-29-3E-5C-00-0C-29-4F-5E-36

DNS-Server . . . . . . . . . . . : 192.168.1.200

NetBIOS über TCP/IP . . . . . . . : Aktiviert

Tunneladapter isatap.{2416AEEA-7BAD-40D9-8081-FF9EFA72DC07}:

Medienstatus. . . . . . . . . . . : Medium getrennt

Verbindungsspezifisches DNS-Suffix:

Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter

Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0

DHCP aktiviert. . . . . . . . . . : Nein

Autokonfiguration aktiviert . . . : Ja

Tunneladapter LAN-Verbindung* 3:

Medienstatus. . . . . . . . . . . : Medium getrennt

Verbindungsspezifisches DNS-Suffix:

Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0

DHCP aktiviert. . . . . . . . . . : Nein

Autokonfiguration aktiviert . . . : Ja

-

regards...Alex

AWo · ‎09-22-2010

Both guests are listet on the same adapter because the host only have one installed (FRITZ! Wlan adapter).

That was not my question, I meant if both IP addresses are configured on the same virtual adapter.

Bridging mode in the Virtual Network Editor ist set to "Automatic"

However, change it to a fixed setting.

Your VMnet8 and your physical LAN (the wireless one) have the same IP subnet. That is not valid and will cause problems.

You need to change the subnet address of VMnet8 with the Virtual Network Editor.

Fix that first and try again.

AWo

VCP 3 & 4

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

am1367 · ‎09-22-2010

OK ... I changed the IP subnet of VMNet8 to 192.168.176.0 ... but that didn't change anything ...

I switched the VM settings to "Bridged" and to "NAT" but I still have no network connection. Btw - I turned the Windows firewall off...

AWo · ‎09-22-2010

I assume the IP address of the virtual host adapter VMnet8 has been changed, too.....?

Disable IPv6 on every connection.

If that doesn't work delete the connection in your guest, remove the virtual NIC from the virtual hardware and reboot the system. Shut it down again, add a virtual NIC and try the "vmxnet(3)" type, not the "e1000". Install the VMware Tools ans try again.

AWo

VCP 3 & 4

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

am1367 · ‎09-22-2010

Yes ... the IP adress of the virtul host adapter VMNet8 is set to 192.168.176.1 - subnet mask 255.255.255.0 - no Gateway and no DNS-Server entries...

Now I will test your other suggestions - thx so far!

Regards...Alex

am1367 · ‎09-22-2010

OK .. maybe I'm too stupid for that 😕 ...

I uninstalled the VMWare tools and the Intel network adapter on the virtual hardware. After a reboot I shut down the VM. And now I am trying to add a virtual NIC. But where can I choose what type of NIC I want to add.

What I am doing: I open the VM settings and click on the add button on the "Hardware" tab. The Hardware Wizard comes up an let me select the "Network connection" (Bridged/NAT/Host-only...) and the Device status...that's it. Where can I chose the type of the NIC?

AWo · ‎09-22-2010

No, you're not too stupid, its me.

You have to choose the adapter by editing the .vmx file of the guest. Change or add the line to:

ethernet0.virtualDev = "vmxnet3"

AWo

VCP 3 & 4

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

am1367 · ‎09-22-2010

ahh..OK...thx!

am1367 · ‎09-22-2010

OK...I changed the vmx file but the VM refused to start up again after I saved the file.

So - not to loose any more time by searching where I typed sth wrong I decided to set up a completely new VM.

I defined all the parameters without powering up the VM. Then I changed the NIC entry in the vmx file as given and started the new VM.

Unfortunately nothing really changed after the Win 7 installation completed :-(. I see the different virtual network adapter but the behaviour is exactely the same as with the E1000....

Here is the new ipconfig:

-

Windows-IP-Konfiguration

Hostname . . . . . . . . . . . . : Win7x64

Primäres DNS-Suffix . . . . . . . :

Knotentyp . . . . . . . . . . . . : Hybrid

IP-Routing aktiviert . . . . . . : Nein

WINS-Proxy aktiviert . . . . . . : Nein

Ethernet-Adapter LAN-Verbindung:

Verbindungsspezifisches DNS-Suffix:

Beschreibung. . . . . . . . . . . : vmxnet3 Ethernet Adapter

Physikalische Adresse . . . . . . : 00-0C-29-4F-5E-36

DHCP aktiviert. . . . . . . . . . : Nein

Autokonfiguration aktiviert . . . : Ja

Verbindungslokale IPv6-Adresse . : fe80::f5ff:a599:167c:24a5%11(Bevorzugt)

IPv4-Adresse (Auto. Konfiguration): 169.254.218.42(Dupliziert)

Subnetzmaske . . . . . . . . . . : 255.255.0.0

IPv4-Adresse . . . . . . . . . . : 192.168.1.27(Dupliziert)

Subnetzmaske . . . . . . . . . . : 255.255.255.0

Standardgateway . . . . . . . . . : 192.168.1.200

DHCPv6-IAID . . . . . . . . . . . : 234884137

DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-14-2B-C7-8B-00-0C-29-4F-5E-36

DNS-Server . . . . . . . . . . . : 192.168.1.200

NetBIOS über TCP/IP . . . . . . . : Aktiviert

Tunneladapter isatap.{9D00F74D-DF56-4F50-9B61-A53826775C47}:

Medienstatus. . . . . . . . . . . : Medium getrennt

Verbindungsspezifisches DNS-Suffix:

Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter

Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0

DHCP aktiviert. . . . . . . . . . : Nein

Autokonfiguration aktiviert . . . : Ja

-

AWo · ‎09-22-2010

O.K. as a workaround, as you have changed tha NAT network to a different subnet, choose from bridged to NAT and enable DHCP for the connection in the guest. Keep IPv6 disabled.

You should receive an IP address from the VMnet8 subnet range, a default gateway and DNS server with a

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

am1367 · ‎09-23-2010

In the meantime I uninstalled the VM Workstation software an reinstalled it completely - but the behaviour is still the same

After following the given work around I am able to access the internet and to see the the host and the guest in the network devices overview. But I need to access the shares on the NAS...and this has an IP of 192.168.1.X ...

Is there any chance to "bridge" the 2 IP ranges?

AWo · ‎09-23-2010

First of all, you should be able to access the NAS shares via the NAT connection.

Second, what do you mean by bridge 2 IP ranges? If you have only one physical IP subnet you can't bridge two different IP ranges to that network. In fact, if you use bridge you do not bridge an IP subnet at all. Bridging means that the virtual NIC gets transparently connected to the physical network. That means you must use the physical network IP addressing scheme in the guest then.

When you use NAT, you connect the guest to a virtual switch/network (called VMnet8) which has its own IP subnet range. That's the reason why the VMnet8 (NAT) IP network address must be different from the physical one (which was not the case in the beginning). The host does the NAT work and routes the packets to the physical network then.

So, as long as your host does not have two NIC's each connected to different IP subnets, there's no need to create two bridges.

Have you tried the bridge again? Remember, do not use automatic bridging, disable IPv6 and disable all firewalls while testing. Set the host connections to "private" or "home".

AWo

VCP 3 & 4

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

am1367 · ‎09-23-2010

Sorry .. that was my fault!

As I tried to connect to the NAS I forgot that my DNS-Server has a different IP-subnet now which means that he can't resolve device names itself...

I tried to connect to the NAS by using the IP adress and everything works fine :-)!! So forget about the last posting ;-)...

Thx so far for your help!!! Without your help I wouldn't have managed that problem!

I will try to bridge the connection as a test this afternoon ...but for now I have to complete the new VM so that the testing (the reason for setting up the VM) can finally begin

Thx again....Alex

All

Windows 7 (x64) NIC connection problems (IPv4)