VM's unable to access network

[forestall]

I have completed a default install of VMware ESXi 5 today.  Everything seems to work, except that the VM's can only ping the host machine.  The VM's cannot ping any machine on the subnet (i.e. any machine not a guest of the ESXi server), nor can they be reached by any machine on the same subnet.

To summarise:

1.  Standard install (single nic)

2.  VM's can ping host

3.  VM's cannot ping (or be pinged by) other non-VM's.

4.  VM's can ping each other.

5.  VM's do not pick up DHCP external to ESXi server.

[Virtualinfra]

Might be the VM port group UP link not is specified.

Put the screen shot of network setting of the vswitch.

[CloudZone]

Hi,

do you have configured the network in esxi?

Do you have configured the virtual switch with an uplink port connected in your switch LAN?

[forestall]

Is this what you were looking for?

[Virtualinfra]

1. Disable the fire wall on the virtual machine

2. enable network discover on the virtual machine

reboot the virtual machine and try ping, if these are not done before.

Award points for the helpful and correct answer by clicking the below tab

[forestall]

Dharshan wrote:

1. Disable the fire wall on the virtual machine

2. enable network discover on the virtual machine

reboot the virtual machine and try ping, if these are not done before.

Award points for the helpful and correct answer by clicking the below tab

This had no effect, the issue still remains.

[CloudZone]

In this case the firewall Aldo block the ping between The vm and the dhcp work

[CloudZone]

In your phisical switch there are VLan configured?

[forestall]

Cloud Zone wrote:

In this case the firewall Aldo block the ping between The vm and the dhcp work

The VM's firewall is disabled.  So, its something else.

[forestall]

Cloud Zone wrote:

In your phisical switch there are VLan configured?

There are no VLANs configured.

[Virtualinfra]

if possible put screen shot of vm network port group properties screen shot

note the below point if you have not checked before

(Optional) If you are using a VLAN, for

VLAN ID, enter a number between 1 and 4094. If you are not using a VLAN, leave this blank.If you enter 0 or leave the option blank, the port group can see only untagged (non-VLAN) traffic. If you enter 4095, the port group can see traffic on any VLAN while leaving the VLAN tags intact.

[forestall]

Dharshan wrote:

if possible put screen shot of vm network port group properties screen shot

No VLANs are configured.

[CloudZone]

Post your network topology, do you have any other firewall in the network?

What kind of Ethernet adapter you choose for vm?

[Virtualinfra]

is the ESXI installed on physical server directly or on vmware workstation.. just to be clear

[cjscol]

So you are saying that Server 001 can ping Server 002 and vice versa but they can not ping anything else or be pinged by anything else?

Please post the output from ipconfig /all from each of the Virtual Machines.

[forestall]

Post your network topology, do you have any other firewall in the network?

What kind of Ethernet adapter you choose for vm?

I will post it soon.

The Ethernet adapter is working fine, I can connect to the ESXi host.  ARP should be fine too.

is the ESXI installed on physical server directly or on vmware workstation.. just to be clear

Bare metal.

Calvin Scoltock wrote:

So you are saying that Server 001 can ping Server 002 and vice versa but they can not ping anything else or be pinged by anything else?

Please post the output from ipconfig /all from each of the Virtual Machines.

The VM's can communicate with themselves and the host management network.  So, it seems to communicate with everything hosted on the VSwitch, but fails when it tries to access the default gateway.

Note that I can use the vSphere and communicate normally to the ESXi host.

One thing I should mention is that I have the ethernet coming out to a D-Link DWL-G730AP.  It converts from ethernet to wireless, as ESXi doesn't support wireless cards natively.

[Virtualinfra]

is the VM IP are in the same range as esxi host 192.168.1.X.

Put the screen shot of management network portgroup. as esxi is able to communicate outside need to check that..

what is the gateway your using on the esxi and vm are they same.. or different. if different use the same...

[forestall]

Here are the details and screenshots people have been requesting.

Firstly, we have an overview of the network setup:

Next we have screenshots of ipconfig for both guest VMs:

and finally, a screenshot of the working management network:

[forestall]

Having played about with configuration over the last week or so, I am thinking that the ARP tables on the D-Link device are not being properly generated.  Either that, or VMware is sending the wrong values to the device.

Anyone had a similar issue?

[a_p_]

After taking a look at the AP's documentation, I think this is rather a configuration/security issue with the AP, allowing only traffic from one MAC address at a time (which in your case is the Management Network's MAC address). I think it should work if the AP is configured in router-mode, which would require that the vSphere setup runs in another IP range though.

Maybe it's just a setting in the AP or the wireless router which needs to be adjusted.

André