vSphere 5.1 U1 Client --“由于远程服务器响应时间过长，命令已超时”
问题:我们正在尝试做什么，
当尝试使用Windows客户端登录vCenter时，当使用VMware会话凭据或手动提供的凭据(DOMAIN\Username)时，会遇到以下错误：
vSphere客户端无法连接到"vCenter“服务器"vCenter”需要很长时间才能做出响应。(该命令已超时，因为远程服务器需要太长时间才能响应。)
viclient-#-0000.log有以下几个方面：
[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单点登录日志并没有显示任何最近的活动，除了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的尝试解决方案:我们如何尝试修复它，
这似乎与VMware KB 2038918和VMware KB 2037408中的信息一致。我尝试遵循VMware KB 2038918中的解析路径，使用SSO帐户(admin@system-domain)连接到vSphere Web客户端，并调整Base，使组的范围比域的基更窄，以防在进行组枚举时遇到超时问题。这没有解决问题，但是我能够成功地测试连接。不过，web客户端似乎只是在爬行，例如，打开“编辑标识源”对话框窗口花了三分钟时间。
在我们的情况下，VMware KB 2037408似乎不适用，因为无论我们是否使用Windows凭据，或者如果我手动提供Active凭据，身份验证都会失败。
我已经重新启动了VMware vCenter服务，并且解决了这个问题，整个vCenter服务器都失败了。这并没有解决这个问题。
环境:我们的东西，神器是它的破坏
来自我的工作站的vSphere客户端和vSphere Web客户端以及来自vCenter服务器的本地身份验证都失败。多个用户的身份验证失败。我验证了所有试图进行身份验证的用户都是vCenter管理员组的成员(通过安装了vCenter的Windows上的本地管理员的成员身份)。
我可以成功地平并连接用作标识源的域控制器的LDAPS端口。
主机服务器没有任何不当的资源消耗。
我们没有对我们的vSphere安装做任何更改，但是我们没有管理目录服务，也没有任何可见性(尽管我无法想象那里发生了什么变化会破坏vCenter SSO)。
我们正在使用vSphere 5.1.0Build 1063329。我使用Firefox27和AdobeFlash12.0.0.70与vSphere网络客户端。vCenter的主机操作系统是Windows 2008 R2 SP1和MS 2012 SP1。
回答 1
Server Fault用户
发布于 2014-03-05 22:49:12
结果是，当我们安装vCenter的SSO时，它会自动检测到它能够检测到的每个Active Directory域。我们的许多部门运行和管理他们自己的Active域，而不是使用我们正在使用的中央企业Active域。这意味着我们在SSO的标识源(Administration > Sign-On and Discovery > Configuration)中有6个相当大的Active Directory域。
消除不必要的身份来源解决了这个问题。
https://serverfault.com/questions/579888
复制相似问题
腾讯云开发者
