Receiving this error when attempting to initiate a console session from the vSphere client 4.0 connecting to the vSphere server 4.0.
Same behavior for all VM's, Win2003, Win2008 and Redhat guest OS.
From the vSphere host Windows 2003 server I can successfully telnet to the server on port 902 with the following reply:
220 VMware Authentication Daemon Version 1.10: SSL Required, ServerDaemonProtocol:SOAP, MKSDisplayPr
otocol:VNC , VMXARGS supported
Also able to resolve by name and ping the vSphere server from the guests and resolve from the ESX host to the guests.
DNS server and AD server seem to be working as expected.
I have tried rebooting the ESX host with no change.
here is my /etc/vmware/config file:
#cat /etc/vmware/config
libdir = "/usr/lib/vmware"
authd.fullpath = "/usr/sbin/vmware-authd"
authd.client.port = "902"
vmware.fullpath = "/usr/bin/vmware"
control.fullpath = "/usr/bin/vmware-cmd"
serverd.fullpath = "/usr/sbin/vmware-serverd"
serverd.init.fullpath = "/usr/lib/vmware/serverd/init.pl"
authd.proxy.vim = "vmware-hostd:hostd-vmdb"
authd.proxy.nfc = "vmware-hostd:ha-nfc"
authd.proxy.nfcssl = "vmware-hostd:ha-nfcssl"
authd.soapServer = "TRUE"
authd.proxy.vpxa-nfc = "vmware-vpxa:vpxa-nfc"
authd.proxy.vpxa-nfcssl = "vmware-vpxa:vpxa-nfcssl"
Connecting directly to the ESX server using the vSphere client I am able
to access the console for the guest VMs.
I can not seem to find any clues on the Community KB boards. Any help will be appreciated. Thanks, -Jeff
