ESX 3.5 looses connection by connecting to the Virtual Center

[brunofernandez]

Hello there

I'm searching allready about 2 days for my problem. Here we go:

Every time I connect the ESX-Host to the Virtual Center I have no problems. After 1 minute i loose the connection of the ESX-Server to the Virual Center.

Also the direct connection with the virtual infrastructure client works.

Special on this connection is, that it goes throw a firewall. But i have opened all neede Ports on the Firewall:

VC to ESX : 443/TCP, 902/TCP, 903/TCP, 27000/TCP, 27010/TCP, 80/TCP, 9000-9100/TCP

ESX to VC : 902/UDP, 27000/TCP, 27010/TCP, 80/TCP, 9000-9100/TCP

Also all needed ESX-Firewall-Ports are open:

Incoming and outgoing ports blocked by default.

Enabled services: nfsClient CIMSLP ntpClient VCB CIMHttpsServer snmpd sshClient vpxHeartbeats LicenseClient sshServer

Opened ports:

Patrol1 : port 1987 tcp.in

hp-sim : port 2301 tcp.in tcp.out

Esxmigration2 : port 902 tcp.out

sim-cert : port 280 tcp.out

EsxMigration1 : port 443 tcp.out

LDAP : port 389 tcp.out

Patrol3 : port 2060 tcp.out

Patrol2 : port 2059 tcp.out

sysgem : port 7251 tcp.in

KerberosPasswordChange: port 464 tcp.out

KerberosClient : port 88 tcp.out

hpim : port 2381 tcp.in tcp.out

I hope you can help me

Greez

[a_p_]

Some suggestions:

- Check the firewall logs for violations from/to the ESX host.

- Check the Managed IP address - http://kb.vmware.com/kb/1008030

- Make sure the DNS resolution works on the ESX host and vCenter

André

[brunofernandez]

Thank you...but all what you said seems to be allright.

[a_p_]

Any errors or hints in the log files?

On the host: vpxa logs in /var/log/vmware/vpx

On vCenter Server: vpxd logs in C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs\

André

[athlon_crazy]

Having same issue recently and as suggested by VMware Tech Support, go for vCenter 2.5 U5

Release Notes

Resolved Issues

This release resolves the following issue:

Firewall Between ESX Server Hosts and VirtualCenter Server Might Drop

an Idle HTTP Connection Between the Hosts and the VirtualCenter Server

and Cause Errors*

This release resolves an issue where if

the HTTP connection between a remote ESX Server host and the

VirtualCenter Server is idle for more than 30 minutes, the firewall

with default session timeout policy drops the idle HTTP connection.

[brunofernandez]

In the LOGs I don't find nothing interesting.

[brunofernandez]

The Virtual Center is the VCenter for ESX 4.

But i have allready some ESX 3.5 Server running on it.

[brunofernandez]

Hello there

Now I have found the problem.

On the Virtual Center was the Windows Firewall activated.

This was the Problem.

I hope this can help maybee somebody.