• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 473
  • Last Modified:

Unable to See Linkd Mode vCenters through vSphere Client

We have configured linked mode between two vCenters. We are able to see both vCenters in Web Client but unable to see through vSphere Windows based client.
0
dhanush_support
Asked:
dhanush_support
  • 2
3 Solutions
 
Haresh NikumbhSr. Tech leadCommented:
Have you tried to restart the vCenter Inventory service on all vCenter Servers involved in the Linked Mode operation?

http://www.definit.co.uk/2012/10/vcenter-5-1-configuring-vcenter-linked-mode/
0
 
asavenerCommented:
What error do you get?  

Typical errors are unable to resolve the name, unknown connection error, or incorrect user name or password.

Unable to resolve means DNS lookup failed.

Unknown connection error means the client couldn't connect on the right ports.  (See this list:  http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012382)

Incorrect user name or password often means that you have to include your domain name with your credentials (in <domain>\<user name> or <user name>@<AD Domain> format).
0
 
dhanush_supportAuthor Commented:
I am getting time out error
Capture.JPG
0
 
asavenerCommented:
Is this a 5.1 installation?

This thread:  http://communities.vmware.com/thread/418853?start=0&tstart=0 describes other folks having similar issues.

Here are several recommended solutions or workarounds:

1) increase the RAM on the vCenter server to at least 8 GB
2) do not check the "use Windows session credentials" checkbox, but rather type in your credentials (with the domain name).
3) Follow this procedure to change from LDAP to Standard:

A. Login to SSO, via web client, using admin@system-domain user.
B. Under Administration > Sign-On and Discovery > Configuration > Edit the Identity source for the Domain.
C. Change your Primary Server URL for your domain from secure LDAP to Standard by changing the URL and port number.

 

Before:

Secure Global Catalog address: ldaps://<global_server>:3269

 

After:
Global Catalog address: ldap://<global_server>:3268
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now