VMware Cloud Community
ArsonSmith
Contributor
Contributor

Problems getting ESX host connected to virtual center

I can connect to ESX host with ssh

I can connect to ESX host with Infrastructure Client

When I try to connect to Virtual Center it is able to use the root:password that I supply and get the general information, but just before the join I get

"Unable to contact the specified host (x.x.x.x). This might be because the host is not available on the network, there's a network configuration problem, or the management services on the host are not responding."

the syslog /var/log/messages on the ESX host say:

May 19 16:21:31 hostname vmware-hostd[2659]: Accepted password for user root from 127.0.0.1

May 19 16:21:38 hostname vmware-hostd[2659]: Accepted password for user root from 127.0.0.1

May 19 16:21:39 hostname passwd(pam_unix)[4265]: password changed for vpxuser

May 19 16:21:39 hostname vmware-authd(pam_unix)[2659]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root

May 19 16:21:42 hostname vmware-hostd[2659]: Accepted password for user vpxuser from 127.0.0.1

I have rebooted the ESX host and restarted Virtual Center to no avail. The authentication failure is the one I'm not sure about.

-Bill

Reply
0 Kudos
5 Replies
athlon_crazy
Virtuoso
Virtuoso

how did u joined the host? via IP or fqdn?

VMware newbie..

Zen Systems Sdn Bhd

www.no-x.org

http://www.no-x.org
Reply
0 Kudos
AndreTheGiant
Immortal
Immortal

Be sure that DNS resolution is working.

It will usefull also for HA.

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
ArsonSmith
Contributor
Contributor

DNS was my first thought and I figured I fixed it when I found the old IP and new IP both returning in a lockup. Called the DNS admin and had him fix it figured that had to be it with the problem looking like it would connect and auth once then get a failure on the second attempt. but 12 hours after the change and still haveing the same problem.

Also just realized that the vmkernel was on the wrong IP address. Fixed that and still get the same error.

rebooting now and will reply with the outcome shortly.

EDIT:

The reboot fixed it. I'm guessing it was because the VMKernel was on the wrong IP address and a reboot was needed (or probably could have just done a service restart) to get services listening again.

Reply
0 Kudos
COdlk
Hot Shot
Hot Shot

I would check the following

- name resolution

- Can you ping the ESX host from the VC by name and by ip?

- restart the management service --> service mgmt-vmware restart

- restart the vmware vpxa service --> service vmware-vpxa restart

Try to reconnect.

david

Reply
0 Kudos
Wimo
Hot Shot
Hot Shot

For the sake of the next person for whom none of the above works - make sure that the directory /tmp/vmware-root exists.

Reply
0 Kudos