I came across the above error under vSphere – ESX 4.0 running under workstation.
To fix it, add the following line to the /etc/vmware/config file in the VMware ESX Service Console:
” vmauthd.server.alwaysProxy=TRUE “
I came across the above error under vSphere – ESX 4.0 running under workstation.
To fix it, add the following line to the /etc/vmware/config file in the VMware ESX Service Console:
” vmauthd.server.alwaysProxy=TRUE “
So this worked after several other fixes did not (or were already accounted for). However, I don’t really accept the fix without an explanation. What is /etc/vmware/config and how, where & when is it used?
Please.
Thank you
And where did you find the information?
Thanks
I am running ESX4i on a remote machine and using vsphere client to log in. Where do i change this when i log in from the client side with vsphere? I can’t seem to find it in the configuration.
Thanks in advance.
I run vsphere client remotely… and on the other end this particular fix has already been employed.. yet i have this issue?
I ran into the same problem and it was the same issue.
To fix it, add the following line to the /etc/vmware/config file in the VMware ESX Service Console:
vmauthd.server.alwaysProxy = “TRUE”
We had the same problem, it was an network error (the port 902 was closed by a firewall). The best thing to discard being that is telneting to that port:
telnet IPADDRESS 902
You should receive something like:
“220 VMware Authentication Daemon Version 1.10: SSL Required, ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC , VMXARGS supported”
Seems Windows 7 was blocking my connection to one of the hosts and only on port 902… I just rebooted windows
I’m having this same issue with ESXi 4.1. “vmauthd.server.alwaysProxy=TRUE” is already in there by default.
Work like charm !!
1. firts try add hosts dns, then ping the host if reply then ..
2. seconds add vmauthd.server.alwaysProxy = “TRUE”
thanks for info
I have the following error “Unable to connect to the KMS: Internal error” but it is not form ESX Server. All the setting in ESX Servers described above are already set. This error happen from Remote Console in vCloud Director.
Any thoughts.