Unable to bridge server to physical network in Workstation 7

[shadowalka]

Hello

Newbie here. I've looked through forums on here and can see that some people have experienced issues trying to bridge virtual machines (VMnet0) to physical networks. Not sure if anyone has come up with a definitive answer so I'll add my scenerio to the mix.

I have set up WMware Workstation 7 on a Windows 7 boot camp partition on my iMac and created a network consisting of 3 Win 2k3 servers, a Win 2k8 server, a Win XP and Win 7 client for testing. These are successfully connected to a Lan called LAN 1 and reside in a domain.

I am trying to set up internet connectivity for this network through the first Win 2k3 server. This server has two network cards - one on LAN 1 and one bridged to my netgear router. I've configured my router to reserve an ip address for the server (192.168.0.5) and manually configure the server's internet/bridge NIC with this ip address.

I am able to ping the router (192.168.0.1) from the vm Win 2K3 server and also my iMac (192.168.0.4). Can also ping the server from my iMac.

I am limiting my internet testing to the server to see if the machine alone can access the network before I try to configure the other machines for access.

Have seen a few suggestions of uninstall, reinstall the VMware bridge protocol for the physical network card as well as restoring the Virtual Network Editor default properties - I've done both suggestions, still can't connect to the network. Also changed the 'bridged to' setting in Virtual Network Editor to the physical netword card, auto bridge setting.

In the server's vm settings, the machine has a list of two network cards - one set to bridged to physical network, the other set to connect to LAN1.

Interesting thing is that the original image (vmware machine used as a template) is still set to NAT and is able to connect to the Internet.

Spend about 6 hours trying a variety of ideas and retracing my steps but to my thinking everything is as it should be .

Is there a bug in Workstation 7 or is there a step that I've missed?

Any ideas would be most appreciated!

[AWo]

Welcome to the forums!

shadowalka schrieb:

I am able to ping the router (192.168.0.1) from the vm Win 2K3 server and also my iMac (192.168.0.4). Can also ping the server from my iMac.

I am limiting my internet testing to the server to see if the machine alone can access the network before I try to configure the other machines for access.

Have seen a few suggestions of uninstall, reinstall the VMware bridge protocol for the physical network card as well as restoring the Virtual Network Editor default properties - I've done both suggestions, still can't connect to the network. Also changed the 'bridged to' setting in Virtual Network Editor to the physical netword card, auto bridge setting.

You can ping the router but you can't reach the internet? Can you ping a host on the Internet from your W2K3 guest by its IP address? If you can ping the router communication works in general.

AWo

[shadowalka]

Thanks for the reply and welcome AWo.

I get no response when I ping www.google.com by name or ip. I forgot to put in my original post that I can access the internet from my iMac (host) with no problems. Confirmed the ip of google as 74.125.230.114 (www1.google.com) from the iMac/Windows 7, request timed out from the server. Firewall is off.

Pheww...this is a brain teaser

[bobby32wf]

What's the result of:

C:>route print

from the host and the guest vm?

[AWo]

Add "ipconfig /all" from host and guest to the "route" post.

AWo

[shadowalka]

Thanks guys for your replies.

As requested.

Virtual Machine:

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0c 29 df 66 51 ...... Intel(R) PRO/1000 MT Network Connection
0x10004 ...00 0c 29 df 66 5b ...... Intel(R) PRO/1000 MT Network Connection #2
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1      192.168.0.5     10
          0.0.0.0          0.0.0.0     192.168.61.2     192.168.61.2     10
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
      192.168.0.0    255.255.255.0      192.168.0.5      192.168.0.5     10
      192.168.0.5  255.255.255.255        127.0.0.1        127.0.0.1     10
    192.168.0.255  255.255.255.255      192.168.0.5      192.168.0.5     10
     192.168.61.0    255.255.255.0     192.168.61.2     192.168.61.2     10
     192.168.61.2  255.255.255.255        127.0.0.1        127.0.0.1     10
   192.168.61.255  255.255.255.255     192.168.61.2     192.168.61.2     10
        224.0.0.0        240.0.0.0      192.168.0.5      192.168.0.5     10
        224.0.0.0        240.0.0.0     192.168.61.2     192.168.61.2     10
  255.255.255.255  255.255.255.255      192.168.0.5      192.168.0.5      1
  255.255.255.255  255.255.255.255     192.168.61.2     192.168.61.2      1
Default Gateway:      192.168.61.2
===========================================================================
Persistent Routes:
  None

C:\Documents and Settings\super_user>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : WinSrv2K3-DC1
   Primary Dns Suffix  . . . . . . . : myOrg.com
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : myOrg.com

Ethernet adapter Public Network:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-0C-29-DF-66-51
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.0.5
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 192.168.0.1

Ethernet adapter Private Network:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
2
   Physical Address. . . . . . . . . : 00-0C-29-DF-66-5B
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.61.2
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.61.2
   DNS Servers . . . . . . . . . . . : 192.168.61.2

Host Machine:

C:\Users\Reggie>route print
===========================================================================
Interface List
16...64 b9 e8 e7 84 2b ......Bluetooth Device (Personal Area Network)
14...d4 9a 20 61 17 7c ......Atheros AR928X Wireless Network Adapter
11...d4 9a 20 f1 ec 7a ......NVIDIA nForce 10/100/1000 Mbps Ethernet
22...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1
23...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8
  1...........................Software Loopback Interface 1
12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
18...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4
20...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #5
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1      192.168.0.4     20
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      169.254.0.0      255.255.0.0         On-link     169.254.113.7    276
    169.254.113.7  255.255.255.255         On-link     169.254.113.7    276
  169.254.255.255  255.255.255.255         On-link     169.254.113.7    276
      192.168.0.0    255.255.255.0         On-link       192.168.0.4    276
      192.168.0.4  255.255.255.255         On-link       192.168.0.4    276
    192.168.0.255  255.255.255.255         On-link       192.168.0.4    276
    192.168.242.0    255.255.255.0         On-link     192.168.242.1    276
    192.168.242.1  255.255.255.255         On-link     192.168.242.1    276
  192.168.242.255  255.255.255.255         On-link     192.168.242.1    276
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link       192.168.0.4    276
        224.0.0.0        240.0.0.0         On-link     169.254.113.7    276
        224.0.0.0        240.0.0.0         On-link     192.168.242.1    276
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link       192.168.0.4    276
  255.255.255.255  255.255.255.255         On-link     169.254.113.7    276
  255.255.255.255  255.255.255.255         On-link     192.168.242.1    276
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
11    276 fe80::/64                On-link
22    276 fe80::/64                On-link
23    276 fe80::/64                On-link
23    276 fe80::5de1:5ed5:d26:c7a8/128
                                    On-link
22    276 fe80::6d3c:2925:f353:7107/128
                                    On-link
11    276 fe80::f02a:d79e:a300:256c/128
                                    On-link
  1    306 ff00::/8                 On-link
11    276 ff00::/8                 On-link
22    276 ff00::/8                 On-link
23    276 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

C:\Users\Reggie>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Reggie-Win7PC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : 64-B9-E8-E7-84-2B
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Atheros AR928X Wireless Network Adapter
   Physical Address. . . . . . . . . : D4-9A-20-61-17-7C
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet
   Physical Address. . . . . . . . . : D4-9A-20-F1-EC-7A
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::f02a:d79e:a300:256c%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.4(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 03 February 2011 18:00:26
   Lease Expires . . . . . . . . . . : 06 February 2011 18:00:26
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 248814112
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-47-D0-65-D4-9A-20-F1-EC-7

   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMne
1
   Physical Address. . . . . . . . . : 00-50-56-C0-00-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::6d3c:2925:f353:7107%22(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.113.7(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 352342102
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-47-D0-65-D4-9A-20-F1-EC-7

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMne
8
   Physical Address. . . . . . . . . : 00-50-56-C0-00-08
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::5de1:5ed5:d26:c7a8%23(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.242.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 369119318
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-47-D0-65-D4-9A-20-F1-EC-7

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{77EBBA2F-2FA5-4051-883A-5D18BD2F81CE}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{91C859FF-953F-44F7-A4A4-B411DC09B7A5}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{2BB97083-5FD8-4088-BDC7-683B9297A6E0}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{70E21BC0-61CC-4B13-835D-E00DCD6A65F7}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{0BEDA54A-5B7F-4A08-8440-DF47941C9B69}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

[continuum]

launch Virtual Network editor - vmnetcfg.exe and create a screenshot - please attach it

[AWo · Accepted solution]

shadowalka schrieb:

Virtual Machine:

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0c 29 df 66 51 ...... Intel(R) PRO/1000 MT Network Connection
0x10004 ...00 0c 29 df 66 5b ...... Intel(R) PRO/1000 MT Network Connection #2
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1      192.168.0.5     10
          0.0.0.0          0.0.0.0     192.168.61.2     192.168.61.2     10
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
      192.168.0.0    255.255.255.0      192.168.0.5      192.168.0.5     10
      192.168.0.5  255.255.255.255        127.0.0.1        127.0.0.1     10
    192.168.0.255  255.255.255.255      192.168.0.5      192.168.0.5     10
     192.168.61.0    255.255.255.0     192.168.61.2     192.168.61.2     10
     192.168.61.2  255.255.255.255        127.0.0.1        127.0.0.1     10
   192.168.61.255  255.255.255.255     192.168.61.2     192.168.61.2     10
        224.0.0.0        240.0.0.0      192.168.0.5      192.168.0.5     10
        224.0.0.0        240.0.0.0     192.168.61.2     192.168.61.2     10
  255.255.255.255  255.255.255.255      192.168.0.5      192.168.0.5      1
  255.255.255.255  255.255.255.255     192.168.61.2     192.168.61.2      1
Default Gateway:      192.168.61.2
===========================================================================

The W2K3 guest, which should act as a router must have its default gateway configured to point to you physical gateway. In you case, it points to itself. This is a dualhomed machine and it should only have configured ONE default gateway, so remove the gefault gateway from the connection 192.168.61.0.

AWo

[shadowalka]

Many thanks to AWo and Bobby32wf.

AWo, you are correct. Changing the default gateway on the Private Network NIC (ever deleting or changing to 192.168.0.1) allows the server/virtual machine to connect to the internet. This shows that vmware bridging works, it was just my configuration on the server.

Thought it would be just a case of having two NICs on the server configured to both my router's network and a private LAN with VMware. Clearly I've got to work out or research how to do this as I still want to allow my clients NAT internet access through the server..this information is probably for another forum!

Many thanks All!