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

ESXi host disconnects from vSphere

Hi, i have a vSphere system with 2 connected host.

Both are behind a firewall and they connect perfectly to the vSphere system.

now i want to connect a 3rd host to this vSphere. I added the host with his public ip adres. when connected to the vSpere it connects and after a few seconds i disconnects again. Now the vSphere has a message that 192.168.1.1 has been disconnected. Even when that ip adres is not the public nor the local ip address. When i add the host with the local adres from behind the firewall the same thing happens after few seconds. he disconnects and displays a 192.168.1.1 disconnected host...

any idea's?
0
Rik Van Lier
Asked:
Rik Van Lier
  • 7
  • 6
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Are firewalls enabled, and do you have the correct rules in place for the host.

Are all these hosts at the same location?

Are you using the correct version of vCenter Server with the correct version of ESXi, e.g. All 5.1, or All 5.5.

e.g. you are not adding 5.5 to vCenter 5.1

Try restarting network management agents...
0
 
Rik Van LierAuthor Commented:
Andrew,

i have nothing changed. On our hardware firewall i have any port open for that public IP. even that does not work. Also when i use the local ip this should not be an issue.

also when i connect to the host itself there is no problem.

and all hosts and vspere are running 5.1
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Can you connect remotely via the vSphere Client to this hosts public IP Address without any issue?
0
Cyber Threats to Small Businesses (Part 2)

The evolving cybersecurity landscape presents SMBs with a host of new threats to their clients, their data, and their bottom line. In part 2 of this blog series, learn three quick processes Webroot’s CISO, Gary Hayslip, recommends to help small businesses beat modern threats.

 
Rik Van LierAuthor Commented:
i can connect internal and external to the vsphere server. but with only 2 hosts instead of 3. the 3rd gives that error i explained.

i can connect with the vsphere client software direcly to the host using the internal and external ip without issues.

only the vsphere server cannot connect to the host it seems.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you logon to the vCenter Server, and issue a "ping" to the ESXi host server, do you get any request timeouts.

Also a restart of the troublesome host may be helpful.
0
 
Rik Van LierAuthor Commented:
ping goes well, no timeout after 10 minutes using option -t

restarting the host i have already done.
0
 
Rik Van LierAuthor Commented:
when i connect using the client to the host directly i got a message that the certificate does not respond well. the ip of the host does not match the host name "localhost" Could that be the reason he jumps in vcenter from the public ip to the 192.168.1.1 and disconnects.

and can i change the hostname without being fysicaly at the server. can this be done using the client or cli?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
This is always normal for the default certificate on a host, that the certificate installed does not match the hostname (fqdn), this should not be the cause of the disconnects.

how is connection performed to the ESXi host via IP Address or DNS name (hostname and fqdn) ?

yes the hostname can be changed, using vSphere Client.

do you have a host file with the hostnames in.....

All these ESXi hosts are at the same location?

You are licensed in vCenter Server for three hosts?

e.g. you have vCenter Server Standard or Essentials ?

You may have to look at the vCenter Server logs..
0
 
Rik Van LierAuthor Commented:
OK, here some news. i connect all hosts using IP Address.

All ESX hosts are at the same location.

We use a VMWare Essentials with allow us 3 hosts.

today a second host has the same problem. And strange.

we have 3 hosts. 1 outside the firewall. 2 behind a firewall. the one behind the firewall have this problem.

also the vcenter is behind the firewall.

do i miss any ports to open? we have inbound 80, 443, 902
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
We need to look at the logs.
0
 
Rik Van LierAuthor Commented:
where can i find this?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
0
 
Rik Van LierAuthor Commented:
owkay there are a lot of log files there. what am i looking for?
0
 
Black_FlagCommented:
We ran into tons of these issues when we implemented our cisco UCS and emc VNX...hosts crashes...disconnecting from the cluster, etc.  You really have to take a deep look into your network configuration and storage configuration.  We found we had many IP address conflicts among other networking issues that the vendor fudged up when implementing the system.  Make sure you don't have a duplicate IP because that could be the culprit.
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

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