VMware Communities
taqi_alshamiri
Contributor
Contributor

VMs bridge mode unable to communicate externally when statically set but they work with DHCP

Hi All,

I am seeking help as I am unable to understand the issue I am having and how to go around it.

The issue I am having is VMs when they are statically set they are not able to reach gateway but when they learn the IP through DHCP they can communicate to gateway and externally fine without any issues.

This is experienced across VMs (Windows, linux, custom built images etc.) in my lab environment. This is true even when firewalls and security products has been disabled on VMs and host machine.

VM workstation version is 16 and tried with 15 and its the same case.

Example below from windows host machine ( statically set).

Ethernet adapter Ethernet0: 

Connection-specific DNS Suffix  . : 

Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection 

Physical Address. . . . . . . . . : 00-0C-29-C8-01-EE 

DHCP Enabled. . . . . . . . . . . : No 

Autoconfiguration Enabled . . . . : Yes 

Link-local IPv6 Address . . . . . : fe80::1125:44a5:3033:10d0%12(Preferred) 

IPv4 Address. . . . . . . . . . . : 192.168.128.246(Preferred)  

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

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

*** ARP is able to learn the host machine IP address and its able to communicate with the host machine fine (host machine IP is 192.168.128.7) VM machine statically set to 192.168.128.246 ***

PS C:\Users\Administrator> arp -a

Interface: 192.168.128.246 --- 0xc   Internet Address      Physical Address      Type

192.168.128.7         2c-30-33-27-1c-73     dynamic

192.168.128.43        00-0c-29-e9-fa-0e     dynamic

192.168.128.255       ff-ff-ff-ff-ff-ff     static

224.0.0.22            01-00-5e-00-00-16     static

224.0.0.252           01-00-5e-00-00-fc     static

PS C:\Users\Administrator> ping 192.168.128.7

Pinging 192.168.128.7 with 32 bytes of data:

Reply from 192.168.128.7: bytes=32 time

C:\Users\Administrator> ping 192.168.128.1

Pinging 192.168.128.1 with 32 bytes of data:

Reply from 192.168.128.246: Destination host unreachable.

Reply from 192.168.128.246: Destination host unreachable.

Reply from 192.168.128.246: Destination host unreachable.

Reply from 192.168.128.246: Destination host unreachable.

Ping statistics for 192.168.128.1:     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

*** Dynamically learnt IP - which works ***

Ethernet adapter Ethernet0:

   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection

   Physical Address. . . . . . . . . : 00-0C-29-C8-01-EE

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

   Autoconfiguration Enabled . . . . : Yes

   Link-local IPv6 Address . . . . . : fe80::1125:44a5:3033:10d0%12(Preferred)

   IPv4 Address. . . . . . . . . . . : 192.168.128.42(Preferred)

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

   Lease Obtained. . . . . . . . . . : Monday, October 19, 2020 7:48:19 PM

   Lease Expires . . . . . . . . . . : Tuesday, October 20, 2020 7:48:19 PM

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

   DHCP Server . . . . . . . . . . . : 192.168.128.1

*** Note, this time I am able to learn the arp from the gateway ***

PS C:\Users\Administrator> arp -a

Interface: 192.168.128.42 --- 0xc

  Internet Address      Physical Address      Type

  192.168.128.1         68-3a-1e-7a-1c-78     dynamic

  192.168.128.7         2c-30-33-27-1c-73     dynamic

  192.168.128.43        00-0c-29-e9-fa-0e     dynamic

  192.168.128.255       ff-ff-ff-ff-ff-ff     static

  224.0.0.22            01-00-5e-00-00-16     static

  224.0.0.252           01-00-5e-00-00-fc     static

  255.255.255.255       ff-ff-ff-ff-ff-ff     static

*** connectivity works as below for DHCP assigned IP ****

PS C:\Users\Administrator> ping 192.168.128.1 -n 1

Pinging 192.168.128.1 with 32 bytes of data:

Reply from 192.168.128.1: bytes=32 time=3ms TTL=64

Ping statistics for 192.168.128.1:

    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 3ms, Maximum = 3ms, Average = 3ms

PS C:\Users\Administrator> ping 192.168.128.7 -n 1

Pinging 192.168.128.7 with 32 bytes of data:

Reply from 192.168.128.7: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.128.7:

    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

PS C:\Users\Administrator> ping 8.8.8.8 -n 1

Pinging 8.8.8.8 with 32 bytes of data:

Reply from 8.8.8.8: bytes=32 time=15ms TTL=118

Ping statistics for 8.8.8.8:

    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 15ms, Maximum = 15ms, Average = 15ms

This is one of the virtual machines network settings and I am not sure how to proceed next to be able to statically assign IP's and resolve the issue.

While its true it works with DHCP and this can be managed with Windows and linux operating system. There are other VM's that you have to statically assign IP like Cisco ISE which I use on my lab.

I tried to set a nested ESXi inside the VM Workstation and its the same case.

Kind Regards

Taqi Al-shamiri

Reply
0 Kudos
0 Replies