No - the IP addresses are all set static, in the same subnet.

Kurt

On Thu, Apr 3, 2014 at 1:41 PM, David McSpadden <[email protected]> wrote:
> Do you notice if those are getting the Microsoft auto configuration ip 
> addresses of 169...
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] 
> On Behalf Of Kurt Buff
> Sent: Thursday, April 03, 2014 4:40 PM
> To: [email protected]
> Subject: [NTSysADM] No communication between VMs on an ESXi host
>
> All,
>
> My search-fu is failing, so I turn to you for help...
>
> I have a small ESXi 5.5 host, about to go into production.
>
> The three VMs (2008R2 for all of them, a DC, Exchange 2010 and a PRTG
> box) on it can communicate with machines not on the ESXi host - ping, RDP, 
> etc. - and vice versa. No problems.
>
> However, the three VMs on this host cannot talk with each other. No ping, no 
> RDP. When pinging from one of the VMs to another, I get a mix of unreachables 
> from the VMs own address and straight timeouts.
>
> There is only one vSwitch, which has two NICs bound to it, and the vswitch is 
> set up to route based on IP hash. The physical switch to which they are 
> connect (and this shouldn't matter, but...) is an HP 2510G-48, and the ports 
> for the host are in a simple trunk - no LACP.
>
> I've turned off the Domain profile of the firewall on one of the machine, 
> which seems to make no difference.
>
> I've examined the VMware host security settings to no avail. I've turned off 
> the Windows firewall.
>
> I've got 3 ESXi hosts in a vSphere Standard cluster that doesn't have this 
> problem.
>
> Kurt
>
>
> This e-mail and any files transmitted with it are property of Indiana Members 
> Credit Union, are confidential, and are intended solely for the use of the 
> individual or entity to whom this e-mail is addressed. If you are not one of 
> the named recipient(s) or otherwise have reason to believe that you have 
> received this message in error, please notify the sender and delete this 
> message immediately from your computer. Any other use, retention, 
> dissemination, forwarding, printing, or copying of this email is strictly 
> prohibited.
>
> Please consider the environment before printing this email.


Reply via email to