Adding an ESXi host to vCenter fails with "Cannot contact the specified host" despite successful ping response
Article ID: 441817
Updated On:
Products
Issue/Introduction
The ESXi Host Client user interface is fully accessible via a web browser; however, adding the host to vCenter fails with the error 'Cannot contact the specified host'.
ICMP pings from the vCenter Server to the ESXi host are successful.
Even though the sshd service is running on the ESXi host, SSH connections from vCenter to this specific host fail, while connections to other hosts succeed.
The vpxd.log indicates a connection timeout when attempting to reach the ESXi host over port 902.
"Failed to connect to <HOST_IP>:902. Details: Connection timed out"
The ESXi host has two VMkernel (vmk) interfaces configured within the same management subnet (potential routing/multihoming conflict).
Environment
VMware ESXi 8.0.x
VMware vCenter 8.0.x
Cause
When multiple VMkernel interfaces on an ESXi host exist in the same subnet, the host may unexpectedly route traffic through an incorrect interface. This behavior disrupts communication between vCenter and ESXi, leading to management failures such as failing to add a host.
Resolution
Remove the unused VMkernel interface residing on the same subnet as the vmk0 management interface. (For more details, refer to the Additional Information section.)
Additional Information
Feedback
