How to Fix Connection issue from WinXP 32 bit vSphere Client to vSphere 5.1/5.5/6.0

For those who are running Windows XP 32 bit and facing the issue while connecting the vSphere Client to connect to vCenter Server 5.5, ESXi 5.5 and ESXi 6.0 host directly, there is a solution provided by VMware.

cant connect vsphere5.5-xp-1
According to VMware KB, this is due to a Handshake failure. vSphere 5.1 and 5.5 uses the Open SSL library, which, for security, is configured by default to accept only connections that use strong cipher suites. On Windows XP or Windows Server 2003, the vSphere Client and vSphere PowerCLI do not use strong cipher suites to connect with vCenter Server. This results in the error No matching cipher suite on the server side, and a Handshake failure on the vSphere Client or vSphere PowerCLI side.

There is a hotfix, KB948963 for Windows Server 2003 32 and 64bit, or Windows XP 64bit.

Note: Windows XP has reached end of support and new hotfixes will not be available.  For more information, see Windows Support Has Ended.

 

Solution for ESXi 5.1 and 5.5

1. Connect to the host via SSH or using ESXi Shell :

~ # vi /etc/vmware/rhttpproxy/config.xml

Insert the following line under vmacore > ssl section, it exactly under <libraryPath>/lib/</libraryPath>

<config>
...
 <vmacore>
...

   <ssl>
          <doVersionCheck> false </doVersionCheck>
          <useCompression>true</useCompression>
          <libraryPath>/lib/</libraryPath>
          <cipherList>ALL</cipherList>
   </ssl>
...
 </vmacore>
...
</config>

2. Save and close the config.xml file
3. Restart rhttpproxy service to take affect :

~ # /etc/init.d/rhttpproxy restart
watchdog-rhttpproxy: Terminating watchdog process with PID 34232
rhttpproxy stopped.
rhttpproxy started.


Solution for the vCenter Server Appliance

  1. Connect to the vCenter Server Appliance via SSH. For more information, see Enable or Disable SSH Administrator Login on the VMware vCenter Server Appliance in the vCenter Server and Host Management Guide.
  2. Navigate to the directory:

    /etc/vmware-vpx/
  3. Backup the vpxd.cfg file. Do not skip this step.
  4. Open vpxd.cfg file in a plan text editor
  5. Add the <cipherList>ALL</cipherList> parameter between the <ssl>…</ssl> section of the configuration file, For example:
    <config>
    ...
    <vmacore>
    ...
    <ssl>
    ...
    <cipherList>ALL</cipherList>
    ...
    </ssl>
    ...
    </vmacore>
    ...
    </config>
    

    xp-vmware-1

  6. Save and close the vpxd.cfg file.
  7. Restart the vCenter Server service for the change to take effect.

 

Solution for Windows-based vCenter Server

  1. Connect to the vCenter Server using RDP.
  2. Navigate to the directory:C:\ProgramData\VMware\VMware VirtualCenter\
  3. Backup the vpxd.cfg file. Do not skip this step.
  4. Open the vpxd.cfg file in a text editor
  5. Add the <cipherList>ALL</cipherList> parameter between the <ssl>…</ssl> section of the configuration file, for example:
    <config>
    ...
    <vmacore>
    ...
    <ssl>
    ...
    <cipherList>ALL</cipherList>
    ...
    </ssl>
    ...
    </vmacore>
    ...
    </config>
    
  6. Save and close the vpxd.cfg file.
  7. Restart the vCenter Server service for the setting to take affect.

5 Comments

  1. churos April 1, 2015
  2. noisome July 27, 2015
  3. shashikanth.bussa September 24, 2015
  4. Greg October 14, 2015
  5. Sebastian Soldini September 28, 2016

Leave a Reply