VMware Infrastructure Client could not establish the initial connection with server
We currently have a ESXi 3.5 install which is running production VM's. When trying to connect directly to the ESXi host with the vic I receive the following error: VMware Infrastructure Client could not establish the initial connection with server "192.168.95.6" Details: A communication error occurred while sending data to the server.
I can Remote Desktop to the VM's on this ESXi Server, I just cannot connect to the ESXi host.
I have tried Restarting the Management Agents at the console but I still cannot gain access to the ESXi host.
Any help would be greatly appreciated.
can you check networking on the host?
try test network option, and ping other servers e.g. DNS servers on your network?
check physical nics are connected?
try test network option, and ping other servers e.g. DNS servers on your network?
check physical nics are connected?
ASKER
The Host and the VM's respond to a ping. Like I said I can RDP to the VM's and the VM's are functioning fine. I just cannot connect o the host using the vic.
Can you check networking on the host?
It could be an issue with management agent on the host not fully starting. That is commonly caused by there being an issue with storage (currently or in the recent past) and the management processes being tied up by various processes that are trying to connect to a lost storage device.
have you had any problems with the system in the recent past?
have you had any problems with the system in the recent past?
ASKER
Testing the management network went fine, no errors. The storage is local storage. There has been no issues with this host in the past.
what is the make/model of the server? there's been a couple of problems with internal cdrom drives when they're USB based.
Have you recently patched the host?
ASKER
The host has not been patched recently and the Server is an HP DL380 G5 with 8 GB of RAM.
from the host can you ping your workstation you are trying to manage from?
no iP address conflicts?
check the mac address in your arp cache, against the servers mac address.
no iP address conflicts?
check the mac address in your arp cache, against the servers mac address.
is your management console on the same vswitch as your vm network? If so, are they using different vlan's?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Patching the system resolved the issue.
can you access the physical console?
it suggests a network fault on service console, physical switch, port or cable or nic?