Connect-VIServer cmdlet slow using logged in users credentials

I have found using the Connect-VIServer cmdlet when connecting to a vSphere 5.5 environment it is slow to login if using the current users session.  i.e.  not specifying a username/password.    When connecting to a vsphere 5.1 environment it is perfectly normal.   And when you specify a credential it logs into the 5.5 environment quite quickly, even if I user the same credentials as the logged in user.

Below is the verbose output of connect-viserver:

PowerCLI C:\> connect-viserver -verbose vcenter

VERBOSE: Attempting to connect using SSPI

VERBOSE: Reversely resolved 'vcenter' to 'vcenter.domain.com'

VERBOSE: SSPI Kerberos: Acquired credentials for user 'domain\username'

VERBOSE: SSPI Kerberos: Successful call to InitializeSecurityContext for target 'host/'vcenter.domain.com'

VERBOSE: Cannot complete login due to an incorrect user name or password.

VERBOSE: SSPI NTLM: Acquired credentials for user ''domanin\username'

VERBOSE: SSPI NTLM: Successful call to InitializeSecurityContext for target ''domain\username'

VERBOSE: SSPI NTLM: Acquired credentials for user ''domanin\username'

VERBOSE: SSPI NTLM: Successful call to InitializeSecurityContext for target ''domain\username'

VERBOSE: Connected successfully using SSPI

VERBOSE: Attempting to connect using SSPI

VERBOSE: Reversely resolved 'vcenter' to ''vcenter.domain.com'

VERBOSE: SSPI Kerberos: Acquired credentials for user ''domain\username'

VERBOSE: SSPI Kerberos: Successful call to InitializeSecurityContext for target 'host/'vcenter.domain.com'

VERBOSE: Cannot complete login due to an incorrect user name or password.

VERBOSE: SSPI NTLM: Acquired credentials for user ''domain\username'

VERBOSE: SSPI NTLM: Successful call to InitializeSecurityContext for target ''domain\username'

VERBOSE: SSPI NTLM: Acquired credentials for user ''domain\username'

VERBOSE: SSPI NTLM: Successful call to InitializeSecurityContext for target ''domain\username'

VERBOSE: Connected successfully using SSPI

 

Name                            Port  User

----                                 ----  ----

vcenter                           443   'domain\username

The environment this is happening on is a 2012r2 server with the following powershell and powercli versions

PowerCLI C:\> Get-PowerCLIVersion

 

PowerCLI Version

----------------

   VMware vSphere PowerCLI 5.5 Release 1 build 1295336

---------------

Snapin Versions

---------------

   VMWare AutoDeploy PowerCLI Component 5.5 build 1262826

   VMWare ImageBuilder PowerCLI Component 5.5 build 1262826

   VMware vCloud Director PowerCLI Component 5.5 build 1295337

   VMware License PowerCLI Component 5.5 build 1265954

   VMware VDS PowerCLI Component 5.5 build 1295334

   VMware VDS vSphere PowerCLI Component 4.1.1 build 000001

   VMware vSphere PowerCLI Component 5.5 build 1295334

 

 

PowerCLI C:\> $PSVersionTable

 

Name                           Value

----                           -----

PSVersion                      4.0

WSManStackVersion              3.0

SerializationVersion           1.1.0.1

CLRVersion                     4.0.30319.34014

BuildVersion                   6.3.9600.17090

PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0}

PSRemotingProtocolVersion      2.2