vSphere 5.1 U1客户端 – “由于远程服务器响应时间太长，所以命令已超时”

问题：我们正在努力做什么

尝试使用VMware vSphere Clientlogin到vCenter时，如果同时使用Windows Sessions凭据或手动提供的凭据（ DOMAIN\Username ），则会出现以下错误：

vSphere Client无法连接到“vCenter”服务器“vCenter”花了很长时间来响应。 （由于远程服务器响应时间太长，命令已超时。）

viclient-#-0000.log具有以下内容：

• 有没有办法找出一个ESX服务器在哪个集群或vCenter？
• 我可以将ESXi主机添加到多个vCenter服务器吗？
• 虚拟中心的任何开源等价物？
• vmware esxi 5，无法创build快照和整合失败，如何删除旧的或合并重做日志？
• 如何从命令行更改vCenter Server Appliance IP？

 [viclient:Critical:M:12] 2014-03-04 15:49:59.008 Connection State[vCenter]: Disconnected [viclient:SoapMsg :M:12] 2014-03-04 15:49:59.009 Attempting graceful shutdown of service ... [viclient:SoapMsg :M:12] 2014-03-04 15:49:59.010 Pending Invocation Count: 0 [viclient:SoapMsg :M:12] 2014-03-04 15:49:59.011 Graceful shutdown of service: Success [ :Error :M:12] 2014-03-04 15:49:59.018 Error occured during login VirtualInfrastructure.Exceptions.LoginError: The server 'vCenter' 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) 

查看vSphere SSO日志没有显示任何最近的活动，除了我读到的ssoAdminServer.log ，表明对标识源的查找是成功的：

 name = kcelliott, domain = ad.state.gov inherited from com.vmware.vim.binding.sso.PrincipalId@2fa38f3c [2014-03-04 16:58:36,301 INFO opID=10C1719C-00000005-54 pool-13-thread-10 com.vmware.vim.sso.admin.vlsi.PrincipalDiscoveryServiceImpl] Vmodl method 'PrincipalDiscoveryService.findPersonUser' invoked by [ User {Name: vCenterServer_2013.12.19_140038, Domain: System-Domain} with role RegularUser] [caller:/10.5.216.251] Find person user {Name: kcelliott, Domain: ad.state.gov} [2014-03-04 16:58:36,310 DEBUG opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.ims.impl.DefaultCommandExecutor] Command com.rsa.admin.SearchIdentitySourcesCommand was executed successfully [2014-03-04 16:58:36,318 DEBUG opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.ims.impl.DefaultCommandExecutor] Command {'com.rsa.admin.LookupIdentitySourceCommand', 'com.rsa.admin.LookupIdentitySourceCommand', 'com.rsa.admin.LookupIdentitySourceCommand', 'com.rsa.admin.LookupIdentitySourceCommand', 'com.rsa.admin.LookupIdentitySourceCommand'} was executed successfully [2014-03-04 16:58:36,318 DEBUG opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.ims.impl.DomainManagementImpl] Got external domain: ad1.state.us [2014-03-04 16:58:36,318 DEBUG opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.ims.impl.DomainManagementImpl] Got external domain: ad2.local [2014-03-04 16:58:36,318 DEBUG opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.ims.impl.DomainManagementImpl] Got external domain: ad3.local [2014-03-04 16:58:36,318 DEBUG opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.ims.impl.DomainManagementImpl] Got external domain: ad.state.gov [2014-03-04 16:58:36,318 DEBUG opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.ims.impl.DomainManagementImpl] Got external domain: ad4.alaska.local [2014-03-04 16:58:36,318 DEBUG opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.impl.KeepAlive] Pinging domain ad5.local [2014-03-04 16:58:36,322 DEBUG opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.ims.impl.DefaultCommandExecutor] Command com.rsa.admin.SearchIdentitySourcesCommand was executed successfully [2014-03-04 17:00:06,215 DEBUG opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.ims.impl.DefaultCommandExecutor] Command com.rsa.admin.SearchPrincipalsCommand was executed successfully [2014-03-04 17:00:06,215 WARN opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.ims.impl.DefaultCommandExecutor] Command 'com.rsa.admin.SearchPrincipalsCommand' executed for 89892 millis [2014-03-04 17:00:06,215 DEBUG opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.impl.KeepAlive] Ping result: null [2014-03-04 17:00:06,215 DEBUG opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.impl.KeepAlive] Pinging domain ad5.local [2014-03-04 17:00:06,221 DEBUG opID= DomainKeepAliveThread com.vmware.vim.sso.admin.server.ims.impl.DefaultCommandExecutor] Command com.rsa.admin.SearchIdentitySourcesCommand was executed successfully 

尝试的解决scheme：我们如何尝试解决它

这似乎与VMware KB 2038918和VMware KB 2037408中的信息一致。 我尝试通过使用SSOpipe理员帐户（ admin@system-domain ）连接到vSphere Web Client并调整组的基本DN以缩小域而不是基于域来防止在VMware KB 2038918中的解决schemepath进行组枚举时出现超时问题。 这并没有解决问题，但是我能够成功地testing连接。 Web客户端似乎只是抓取，例如，它需要花费三分钟来打开“编辑身份源”对话窗口。

VMware KB 2037408似乎不适用于我们的情况，因为无论我们是否使用Windows会话凭据或手动提供Active Directory凭据，身份validation都会失败。

我已经重新启动了VMware vCenter服务并解决了问题，即整个vCenter服务器。 这并没有解决这个问题。

环境：我们的东西，神圣的破坏

来自我的工作站的vSphere Client和vSphere Web Client身份validation都失败，vCenter Server中的本地身份validation也失败。 多个用户的身份validation失败。 我validation了所有尝试进行身份validation的用户都是vCenterpipe理员组的成员（通过vCenter Server上安装的Windows服务器上本地pipe理员的成员身份）。

我可以成功地ping和连接用作标识源的域控制器的LDAPS端口。

主机服务器没有任何不适当的资源消耗。

我们没有对vSphere安装进行任何更改，但我们没有pipe理或查看我们的目录服务（尽pipe我无法想象会发生什么样的改变会破坏vCenter SSO）。

我们正在使用vSphere 5.1.0 Build 1063329.我正在使用Firefox 27和带有vSphere Web Client的Adobe Flash 12.0.0.70。 vCenter的主机操作系统是Windows Server 2008 R2 SP1和MS SQL 2012 SP1。