VMware ESXi 5.0 - Unable to connect via vSphere Client 5.5 installed on Windows 8

for 5.5 I think you should use the VMware-viclient-all-5.5.0-1281650.exe

Maybe here....
http://jim-zimmerman.com/?p=979

Go to properties and select compatibly, then select XP Service pack 3, and install. After that connect to the server, it should work.

Please try the suggestion made by "Santasi24" in the post above.

If that doesn't help, you can access vCenter via web from windows 8

Launch browser and type https://ip_address_of_esx_host:9443  (by default 9443 is the port number for SSL web connection) - (If you have modified the port to a different value, enter the same)

You will be able to perform all the tasks that you can via vSphere Client.

If you have a need to use VMware vSphere Client 5.5, it's recommended now, that you switch and start using the VMware vSphere Web Client, because you cannot access all the features of vSphere 5.x, from the vSphere Client.

So time to switch.

None of the solutions helped me. I am trying to build a new setup and initially there will be no vCenter server. I can understand the drawback of not having vCenter server, but my simple question is that why not I am able to connect to the ESXi 5.0 server with vSphere Client "VMware-viclient-all-5.5.0-1281650" installed on Windows 8.0?

Can you please confirm me whether vSphere Client 5.5 is compatible with ESXi 5.0 or not? Will it only work with ESXi 5.5?

ESXi 5.5 client is used to connect to 5.5 when connecting to ESXi 5.0 it downloads and installs ESXi 5.0 client because it needs those DLLd from that client.

The issue is 5.0 client is not compatible with Windows 8

Follow this article

http://brianragazzi.wordpress.com/2012/08/21/windows-8-how-to-install-the-vsphere-client-5-0-update1a/

Thanks for the update. That means it is not possible to connect to ESXi 5.0 through vSphere 5.5 installed on Windows 8. Am I right?

Will it work for vSphere 5.1? Please see the below article-

http://buenoflex.com/archives/185

lets just rewind here...

what version of ESXi do you have?

I have "VMware ESXi 5.0.0 (VMKernel Release Build 469512)".

I've just had to get to the office this evening, so I'm going into one of our Labs to check this for you.

okay, I'm testing against 5.0.0 Patch 7 which is Build 768111, you have 5.0.0 Build GA.

For yourt information, when you click the vSphere Client *.EXE Icon, this is a Launcher file, which detects "which" client it needs to load to connect to the correct version of ESXi.

So if you have installed ESXi 5.5 Client, and try to connect to ESXi 3.5, 4.0, 4.1, 5.0 or 5.1, it will request and download a specific client which needs to be installed to connect to that server version.

If you only have ESXi 5.0 in your organisation, the simplest way, is just to install the 5.0 client. BUT there have been installation issues with the 5.0 client and Windows 8.0, because Windows 8.0 was released after ESXi 5.0 was released!

Let me carry on checking....

I have installed 5.0 client by changing the Compatibility Mode to "Windows 7" and it installed smoothly on Windows 8. I also able to connect to the ESXi server. The only problem is that when I am trying to install a Guest VM, the Console is showing the following message and nothing is happening.

"The VMRC console has disconnected....attempting to reconnect" (please see the attached screenshot).

I have also tested with client VMware-viclient-all-5.1.0-1235233, but facing same issue just like 5.5 client.
VSphere-5.0-Error.png

Okay, so you have successfully installed the client, by changing compatibility mode.

5.1 and 5.5 clients will not help your issues, they are NOT used when connecting to 5.0.

Changing to compatibility mode, "is a hack" really, to get it installed.

which version did you install?

It's VMware-viclient-all-5.0.0-455964

Superb!!!! The explanation is awesome. Thanks a lot for the right solution. VMware-viclient-all-5.0.0-913577.exe is working fine on Windows 8. I am able to work on ESXi 5.0 console as well.

Great solution. :)

Thanks for your comments, it's always best to do it properly, rather than " hack job " solution!

Glad you are up and working correctly!