VMware Communities
Fraethir
Contributor
Contributor

Using WS8, host Win7x64, guest (multiple OSes), bridged NIC fails for non-local subnets

I'm running Workstation version 8.

Host OS is Win7x64

Router is a Cisco RV220W.

Two guest OSes have been tried. Ubuntu 10.4, and Win7x64.


In both cases, if I select Bridged networking, I can ping local subnet hosts, but cannot ping any internet addresses from the guest. I can ping the router gateway from the guest. I can ping local subnets, the guest, and Internet addresses from the host. I am receiving DHCP from the router, so an address is fetched (thus the working fine on the local subnet).

I have reset the VMNet settings to default based on another post (with much hope), but it didn't affect anything.

The bridge service is running.

The mac address for the guest does not duplicate the host, or anything else.

In the Ubuntu guest, I've verified that iptables (firewall) is not messing with anything, and that the default route is being created correctly.

(Guest)

# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0c:29:9b:c0:f6 
          inet addr:192.168.3.138  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:fe9b:c0f6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:488 errors:0 dropped:0 overruns:0 frame:0
          TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:48407 (48.4 KB)  TX bytes:5549 (5.5 KB)

# ping 192.168.3.1
PING 192.168.3.1 (192.168.3.1) 56(84) bytes of data.
64 bytes from 192.168.3.1: icmp_seq=1 ttl=64 time=2.00 ms
64 bytes from 192.168.3.1: icmp_seq=2 ttl=64 time=0.628 ms

# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

# ping 192.168.3.99
PING 192.168.3.99 (192.168.3.99) 56(84) bytes of data.
64 bytes from 192.168.3.99: icmp_seq=1 ttl=128 time=0.361 ms
64 bytes from 192.168.3.99: icmp_seq=2 ttl=128 time=3.83 ms
^C
--- 192.168.3.99 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms

Host:

Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix  . : Cisco
   Link-local IPv6 Address . . . . . : fe80::f109:3a72:17dd:daa6%10
   IPv4 Address. . . . . . . . . . . : 192.168.3.99
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.3.1

C:\Users\Paul>ping 192.168.3.1

Pinging 192.168.3.1 with 32 bytes of data:
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64
Reply from 192.168.3.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.3.1:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
C:\Users\Paul>ping 192.168.3.138

Pinging 192.168.3.138 with 32 bytes of data:
Reply from 192.168.3.138: bytes=32 time<1ms TTL=64
Reply from 192.168.3.138: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.3.138:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
C:\Users\Paul>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=17ms TTL=53
Reply from 8.8.8.8: bytes=32 time=17ms TTL=53

Ping statistics for 8.8.8.8:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 17ms, Average = 17ms
Control-C
^C

Guest operation is fine as NAT with a few notable problems (like not being on the local subnet for some of the tasks I'm trying to do, and not being able to remote into the guest from afar in its current iteration). But those problems with NAT are why I want it to exist as bridged.

Prior to Workstation 8 (v7 and before), I never had a problem with bridged networking behaving as expected. I see a LOT of problems happening with this on 8. Must I spend more to go to 9 to rectify this? It appears something free (like VirtualBox) doesn't have this issue.

--

Paul

Reply
0 Kudos
1 Reply
Fraethir
Contributor
Contributor

Note: took the Ubuntu VM, and used a copy of the hard drive files for a VirtualBox vm (with bridged networking set). As soon as the tools were loaded into the vm the bridged NIC worked fine, unlike with Workstation 8/vmware tools. I'm not sure where the problem lies, but am relatively sure it is not with the composition or configuration of either VM at this point (as the internal virtual configuration didn't change between platforms but the functionality did). I assume I need a new version of the Linux x86/64 vmware tools or somesuch to make the NIC more compatible with bridged? But that's entirely speculation. Real answers, or specific things to check, VERY welcome.

Checking the vmware dist, my currently installed tools are:

8.8.5 (VMwareTools-8.8.5-893888.tar.gz)

My workstation build# is:

8.0.5 build-893925

--

Paul

Edit: As it's been months, and NO ONE has any suggestions (Particularly disappointed that I can't even swing a SWAG from VMWare associated entities), moving to virtualbox and giving up on the solution I actually paid money for thinking it was a more stable and functional business decision.

Reply
0 Kudos