Unable to log in to vSphere Client using Windows session credentials with an account with multiple group memberships.

• VMware vSphere 5.5

Symptoms:

• You are unable to log in to vSphere Client when you select Use Windows session credentials.
• You are able to log in to vSphere Client by manually entering user credentials.
• You are able to log in to the vSphere Web Client using Windows session credentials and by manually entering user credentials.
• This issue occurs when you log in with an account with multiple group memberships in Active Directory or OpenLDAP directory.
• The viclient-#-0000.log file (located at: C:\Users\username\AppData\Local\VMware\vpx\) contains entries similar to:
  
  [viclient:Critical:M: 6] YYYY-MM-DD 10:39:30.213 Connection State[psivmc001.pshosting.intranet]: Disconnected
  [viclient:SoapMsg :M: 6] YYYY-MM-DD 10:39:30.213 Attempting graceful shutdown of service ...
  [viclient:SoapMsg :M: 6] YYYY-MM-DD 10:39:30.215 Pending Invocation Count: 0
  [viclient:SoapMsg :M: 6] YYYY-MM-DD 10:39:30.216 Graceful shutdown of service: Success
  [ :Error :M: 6] YYYY-MM-DD 10:39:30.223 Error occured during login
  VirtualInfrastructure.Exceptions.LoginError: The server 'vCenter_Server_FQDN' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
  at VirtualInfrastructure.LoginMain.Process(BackgroundWorker worker, DoWorkEventArgs e)
  at VirtualInfrastructure.LoginWorkerImpl.Worker_DoWork(Object sender, DoWorkEventArgs e)
  ...
  at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
  VirtualInfrastructure.Exceptions.RequestTimedOut: The request failed because the remote server 'psivmc001.pshosting.intranet' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)