Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >

KB-4165: How does the Centrify adclient connect to a Domain Controller?

Authentication Service ,  

12 April,16 at 11:07 AM

Applies to: Centrify DirectControl on All Versions
How does the Centrify adclient connect to a Domain Controller?
The sequence is as follows:
  • Centrify's adclient selects a DC first by site and it knows the correct site to use by doing an LDAP ping to (any) DC.
  • It does a DNS SRV query for _ldap._tcp.<site>._sites.<domain> to get list of DCs to try first.
  • Then it loops through the list and probes the ports.
Any DC that does not meet the port requirement, is considered not-eligible. (See KB-0029: Firewall port settings for Centrify DirectControl for the list of required ports)
Adclient goes through each DC until it finds a good one. 
If the site list is exhausted without finding any usable DCs, it does a DNS SRV query for _ldap._tcp.<domain>, i.e. Every known DC in the domain.
Adclient will try this list until it finds one to use within a reasonable response time. If it cannot find any one to use, then it goes into Disconnected mode.
Please refer to the following KB article to verify the health of the Domain Controller from Centrify adclient: