• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1442
  • Last Modified:

vmware guest to vmware guest can not communicate

Hi everyone - maybe someone has seen this?

Our VMware guests from different VM servers cannot communicate. The guests can communicate with everything else (physical servers in and out of the same VLAN, internet, etc).The guests are in the same VLAN show the correct ARP entries.

The guests can communicate with other guests on the same vSwitch on the same VMserver - but not with different VMserver's.
The guests can communicate with other guests on different VMServers on different VLANs.

This happens with Windows and Linux guests. The Windows guests do not have the Windows firewall on. The guests are running on ESX 3i on HP Servers and the core network switch is an HP 5400. The core switch (which is responsible for VLAN routing) can communicate with every guest.

If anyone could suggest something to try I would give it a try.

Thanks

0
dustnik
Asked:
dustnik
  • 5
  • 3
2 Solutions
 
65tdCommented:
Ping works OK both IP and host name?
Review TCP/IP configuration.
0
 
dustnikAuthor Commented:
no - ping does not work when the guests are on differnt VMservers. the guests are using the host names correctly. i have tried setting from static to dhcp but it dod not help
0
 
65tdCommented:
The guests can ping locally?
Can the guests ping gateways on each of the host VM networks?

Are the vlans trunked or is it single vlans (subnets) / network card?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
dustnikAuthor Commented:
yes - the guests can ping locally
yes - the guests can ping the default gateway

the vlans are trunked / multiple cards - I did change servers to use one NIC (removed trunking) but it did not help
0
 
65tdCommented:
Are the trunks setup as described in this doc?

http://www.vmware.com/pdf/esx3_vlan_wp.pdf

0
 
dustnikAuthor Commented:
thanks 65td - I double checked the network using the vmware doc but it did not work

But I did find that 1 guest can communicate. The one that can communicate has its IP address in the range of the "Observed IP ranges" (from the vSwitch - network adapters tab). None of the other guests has IP numbers in the Observed IP ranges.

I do not know if this would make a difference or how to change it (or if it means anything important)?

0
 
dustnikAuthor Commented:
thanks 65td

the problem has been fixed. the VM Machine Port Group 'Load Balancing' was set to 'MAC Hash' - after changing it to 'IP Hash' the problem went away (I do not know why - it was MAC Hash for months).
0
 
dustnikAuthor Commented:
.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now