host and guest cannot ping each other with bridged networking

[Foodyborris]

I have a win10 host with a debian jessie guest and bridged networking. Host and guest can access everything they should, except they cannot access/ping each other. win10 exports a mount over smb and the linux mounts it and this gives me a shared partition. It has worked in the past. Sometime (maybe a few months ago?) it stopped working. It turns out that host and guest cannot ping each other at all. I also tried a quick new guest and it has the same problem. I also tried the work laptop and host/guest cannot ping each other with bridged networking. And a friend with a winxp guest inside win10 host also cannot ping between each other. This has worked in the past as I used guest accessing host for the shared partition.

Windows 10 Pro version 1607 OS Build 14393.693

VMware® Workstation 12 Player 12.5.1 build-4542065

Is there any magic hoop jumping required now? Or maybe has a small bug crept in and gone unnoticed for a while? I'm thinking I shouldn't have to do anything other than say bridged networking. I've tried reinstalling etc. The fact that at least 3 independent machines exhibit the same issue suggests it's more subtle (or blunt!) than me messing up my home desktop though. Any help much appreciated.

Thanks

Borris

[jpsider]

Have you enabled icmp?

[Foodyborris]

Host can ping other local and remote addresses and guest can ping other remote and local addresses. I haven't performed any specific icmp enable - I'm not certain where I'd be enabling it. But the problem started after guest could not smb mount host, so if it was a case of enabling icmp somewhere, would there also be somewhere to enable smb traffic as well?

[jpsider]

I think out of the box windows now blocks ping/icmp. You can create a quick firewall rule to allow it. but if it were working before, no patch would dis allow it. So I am not sure what changed in your environment.

[Foodyborris]

We did try disabling Windows firewall during an evening of prodding and investigating - it didn't make any difference we could see.

[jpsider]

what happens when you trace route from one machine to another?

[Foodyborris]

From the win10 host:

C:\Users\Borris>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Cheetah

   Primary Dns Suffix  . . . . . . . :

   Node Type . . . . . . . . . . . . : Hybrid

   IP Routing Enabled. . . . . . . . : No

   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : Intel(R) 82579V Gigabit Network Connection

   Physical Address. . . . . . . . . : C8-60-00-CB-64-A8

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

   Link-local IPv6 Address . . . . . : fe80::a8cb:6862:4035:5d8a%4(Preferred)

   IPv4 Address. . . . . . . . . . . : 192.168.111.130(Preferred)

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Lease Obtained. . . . . . . . . . : 18 January 2017 23:43:23

   Lease Expires . . . . . . . . . . : 21 January 2017 11:43:17

   Default Gateway . . . . . . . . . : 192.168.111.1

   DHCP Server . . . . . . . . . . . : 192.168.111.1

   DHCPv6 IAID . . . . . . . . . . . : 248012800

   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-10-21-03-C8-60-00-CB-64-A8

   DNS Servers . . . . . . . . . . . : 192.168.111.1

   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1

   Physical Address. . . . . . . . . : 00-50-56-C0-00-01

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

   Link-local IPv6 Address . . . . . : fe80::c895:2f0c:21bb:ee17%14(Preferred)

   IPv4 Address. . . . . . . . . . . : 192.168.234.1(Preferred)

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Lease Obtained. . . . . . . . . . : 18 January 2017 23:43:20

   Lease Expires . . . . . . . . . . : 20 January 2017 18:58:12

   Default Gateway . . . . . . . . . :

   DHCP Server . . . . . . . . . . . : 192.168.234.254

   DHCPv6 IAID . . . . . . . . . . . : 419450966

   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-10-21-03-C8-60-00-CB-64-A8

   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 VMnet8

   Physical Address. . . . . . . . . : 00-50-56-C0-00-08

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

   Link-local IPv6 Address . . . . . : fe80::31b7:17a:cb80:b583%12(Preferred)

   IPv4 Address. . . . . . . . . . . : 192.168.220.1(Preferred)

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Lease Obtained. . . . . . . . . . : 18 January 2017 23:43:23

   Lease Expires . . . . . . . . . . : 20 January 2017 18:58:13

   Default Gateway . . . . . . . . . :

   DHCP Server . . . . . . . . . . . : 192.168.220.254

   DHCPv6 IAID . . . . . . . . . . . : 436228182

   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-10-21-03-C8-60-00-CB-64-A8

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

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

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

   Primary WINS Server . . . . . . . : 192.168.220.2

   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)

   Physical Address. . . . . . . . . : 00-26-83-39-AB-83

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{10E3ABBC-B66A-4172-AAA1-216CBA77D5CA}:

   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 isatap.{70113610-C8ED-4C94-A091-EE835BCBF465}:

   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.{7C783400-A7CC-47EA-8D30-E5F431F43963}:

   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

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   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

   IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:381b:3a55:a9f6:3a61(Preferred)

   Link-local IPv6 Address . . . . . : fe80::381b:3a55:a9f6:3a61%2(Preferred)

   Default Gateway . . . . . . . . . : ::

   DHCPv6 IAID . . . . . . . . . . . : 117440512

   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-10-21-03-C8-60-00-CB-64-A8

   NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\Borris>tracert 192.168.111.81

Tracing route to 192.168.111.81 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  Office-wifi [192.168.111.1]

  2     *        *        *     Request timed out.

  3     *        *        *     Request timed out.

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *     ^C

C:\Users\Borris>

From the linux guest

borris@lynx:~$ ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

       valid_lft forever preferred_lft forever

    inet6 ::1/128 scope host

       valid_lft forever preferred_lft forever

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

    link/ether 00:0c:29:71:a1:91 brd ff:ff:ff:ff:ff:ff

    inet 192.168.111.81/24 brd 192.168.111.255 scope global dynamic eth0

       valid_lft 83207sec preferred_lft 83207sec

    inet6 fe80::20c:29ff:fe71:a191/64 scope link

       valid_lft forever preferred_lft forever

borris@lynx:~$ traceroute 192.168.111.130

traceroute to 192.168.111.130 (192.168.111.130), 30 hops max, 60 byte packets

1  lynx (192.168.111.81)  2997.998 ms !H  2997.920 ms !H  2997.917 ms !H

borris@lynx:~$ /sbin/ifconfig

eth0      Link encap:Ethernet  HWaddr 00:0c:29:71:a1:91 

          inet addr:192.168.111.81  Bcast:192.168.111.255  Mask:255.255.255.0

          inet6 addr: fe80::20c:29ff:fe71:a191/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:5454 errors:0 dropped:0 overruns:0 frame:0

          TX packets:2968 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:3346078 (3.1 MiB)  TX bytes:417600 (407.8 KiB)

lo        Link encap:Local Loopback 

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:4205 errors:0 dropped:0 overruns:0 frame:0

          TX packets:4205 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:273028 (266.6 KiB)  TX bytes:273028 (266.6 KiB)

borris@lynx:~$

[jpsider]

‌what kind of router do you have? It appears your gateway/router doesn't know where the hosts are.

[SLAT]

Hi jpsider,

Borris' host has IPv4 Address 192.168.111.130/24 and his Linux Guest has 192.168.111.81/24. That's the same subnet and host and guest are bridged by VMware. Correct me if I overlooked something, but there shouldn't be any routing involved. The routing table on the host should look like this:
C:\Users\Borris>netstat -rn
...
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    192.168.111.1  192.168.111.130     10
...
The guest should look almost the same, except it has 192.168.111.81 as Interface. Since the gateway is correct, host as well as guest can communicate correctly to the rest of the world as Borris stated 20.01.2017 08:14.

[paintcheck200]

I cannot reproduce your issue with Workstation 12.5.2 build-4638234

[SLAT]

Hi Borris,

could you please check your bridging: I can only describe it for VMware Workstation, VMware player may require similar actions.

Chose "Edit | Virtual Network Editor" from the menu.

You may have to click on "Change Settings" (Administrator privileges are required to modify the network configuration)

The upper part of the window should show VMnet0 (Bridged), VMnet1 (Host-only) and VMnet8 (NAT).

Click on the line starting with VMnet0, Bridged

It will most likely show "Auto-bridging"

Click on the button "Automatic Settings"

It will show, all adapters eligible for bridging.

A common reason for the problem you describe can be, that the wrong adapter is selected. Wi-Fi adapters for instance are primary suspects to cause such an error.

I suspect that your "Intel(R) 82579V Gigabit Network Connection" is the only good adapter. Uncheck the rest!

Best Regards,

[aotto]

Chose "Edit | Virtual Network Editor" from the menu.

You may have to click on "Change Settings" (Administrator privileges are required to modify the network configuration)

The upper part of the window should show VMnet0 (Bridged), VMnet1 (Host-only) and VMnet8 (NAT).

Click on the line starting with VMnet0, Bridged

It will most likely show "Auto-bridging"

Click on the button "Automatic Settings"

It will show, all adapters eligible for bridging.

A common reason for the problem you describe can be, that the wrong adapter is selected. Wi-Fi adapters for instance are primary suspects to cause such an error.

I suspect that your "Intel(R) 82579V Gigabit Network Connection" is the only good adapter. Uncheck the rest!

Had the same issue and this solved it.

Thanks, man!

[Sach76]

Hi,

I have similar issue over here i have install VM workstation on windows 2016 server, VM guest is Windows 2008 server with bridge interface setting.

Able to ping and access network Host windows 2016 server and as well all network resources. But cannot access VM guest (windows 2008) from LAN.

i have disable windows firewall and windows defender too.

Please assist me to fix this issue.

[dmac555]

Hi,

I have the same issue. Using virl 1.5\on workstation 14..i cant even ping my default gateway after initial install.

Any help will be appreciated.

Thanks

D

[Conjur]

It's months later but THANK YOU!

I can now send UDP packets from my VM to my host to make it easier to test certain things

[adipose]

See here:

https://superuser.com/questions/617696/vmware-workstation-bridged-network-host-unreachable

Make sure you do not have DNE LightWeight Filter (Citrix) checked on your host's network adapter.

[kshelton]

 I realize that I am Necro'ing a thread, but I have to say "Thank You". I have been looking for a solution for a week and nothing I have found mentioned the DNE Lightweight Filter. I un-ticked the box on my adapter and everything began to work correctly! Thank you again for the help.

[nialeph]

NEVER too late for a "thank you"! 

[Medievaldes]

So many thanks dude! Had the same issue, this fixed it.

Can't thank you enough.

[hiuray]

@adipose Thank you again. I have solved my conenctivity problem by disabling DNE LightWeight filter.

[ViRtUaL739]

Thank You!! Totally worked, Workstation 17

[VMware Community Member]

Unchecking DNE on host's network adapter resolved my issues!

I know it's a bit late for me as well... but thank you SO VERY KINDLY!!

Your friend in Virginia,

Paul L.

[sdbhabal]

Disabling DNE LightWeight filter done the trick for me.

Many thanks.

[Nikhil_129]

If the host and guest operating systems in a virtual machine environment cannot ping each other using bridged networking, it could be due to several reasons, including:

1. Incorrect network settings: Verify that the IP addresses, subnet masks, and default gateways are set correctly on both the host and guest machines.

2. Firewall restrictions: Ensure that the firewall is not blocking ICMP (ping) packets on either the host or the guest.

3. Driver compatibility issues: Some virtualization software requires special network drivers to be installed on the guest operating system to support bridged networking.

4. Virtualization software configuration: Verify that the virtualization software is configured correctly for bridged networking and that the correct network adapter is selected for bridging.

5. Network connection issues: Make sure that both the host and guest machines are connected to the same network and that the network connection is working properly.

If you are still facing this issue, you can check the logs or error messages generated by the virtualization software and the host and guest operating systems for more information.