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

VMs on the same host cannot communicate

I have 2 VMs on the same ESXi 5.0 host, on the same vmswitch; they are the only VMs on this host.  They can communicate with the rest of the network with no problem and they can also browse the Internet, but they cannot ping or browse each other. The Windows firewall is turned off on both machines.  I have eliminated any DNS issues (one of the machines is DC and DNS server, and there is another DC/DNS server on the network as well), TCP/IP configuration issues, etc.  File and Printer Sharing is turned on for both servers. One is running Windows 2008R2 Standard, and the other is Windows 2008 Standard. The only conclusion I can reach is that it's something in the ESXi configuration.  Any ideas would be appreciated.
0
Hypercat (Deb)
Asked:
Hypercat (Deb)
1 Solution
 
ajeabCommented:
did you check gateway setting?
0
 
Hypercat (Deb)Author Commented:
Yes, as I said, both machines can browse the Internet, so their gateway settings are correct.
0
 
David Johnson, CD, MVPOwnerCommented:
are they in the same subnet and vlan?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Have you checked ALL the network settings are the same, Subnet Mask ?

Firewall Disabled on both Hosts?

VMXNET3 interface installed, and VMware Tools ?
0
 
Hypercat (Deb)Author Commented:
@david - There is only one vlan. All devices at this site are in the same subnet, so if one or both of these machines had the wrong subnet, they wouldn't be able to communicate with anything else on the network.  This is a very simple network, about 65-70 devices total, one network/subnet, one hardware firewall router at the edge.

@andrew - same answer on the network settings.  Windows firewall is disabled by group policy, but I double-checked and it is definitely disabled for all profiles. They are using an E1000 driver for the network interface. I've never had a problem with these, but I could change it if you think it might fix the problem.  VMWare Tools are installed and the service is running.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Never use the E1000 for production, only use E1000 for installation.

Replace with VMXNET3, many more benefits.
0
 
Mark GalvinManaging Director / Principal ConsultantCommented:
Have you checked DNS is configured correctly?
0
 
Hypercat (Deb)Author Commented:
Changing to the VMXNET3 driver even on just one of the virtual machines fixed the problem. I'm amazed that this made such a difference, especially since when you create a new virtual machine, ESXi defaults to using the E1000 driver for the NIC card. IMO, they ought to change this default if using the older driver can cause this kind of problem on the newer versions of ESXi.  Thanks!
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

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