This was an issue with domain controllers running on Windows Server 2003 and earlier versions. Note: In the case of a domain controller going down for maintenance purposes, the tool will not know and will fail to connect. On the other hand, if no domain controller is available then that “error” message will be displayed.DC Locator stores the site information for the computer in above registry entry.If the domain controller is available, allow the active directory tools to execute other calls to connect to the active directory database to be displayed in the tool’s console.DC Locator receives the list and pings to make sure domain controller is available and contactable.DNS Server receives the query and responds back with a list of domain controllers.Based on the above results, DC Locator builds the DNS Query and sends out it to DNS Server to find a list of domain controllers.If this is the first attempt by the tool to get a list of domain controllers from DNS Server, or if local computer does not have the DynamicSiteName registry entry created, then build a general DNS Query to find domain controllers. If registry is found then build the DNS Query with site name added to it. Checks to see which active directory site the local computer belongs to by querying the DynamicSiteName registry entry at “HKLM\System\CurrentControlSet\Services\Netlogon\Parameters” key. To build the DNS Query, DC Locator component uses the following strategy: There are two types of DNS queries “DC Locator” component can build and send “ Site-Specific DNS Query” and “ Global DNS Query“. Build a DNS Query to be sent out to DNS Server.As part of the “DcGetDCName” API call, the following actions are taken:.DC Locator executes “DcGetDCName” API call.An active directory tool calls the DC Locator component to find an available domain controller.To explain the steps in more detail, the active directory tools will take the following actions: You will receive the above error message if tool is not able to perform these two steps successfully.
In any case, the DNS Server should be able to return a list of domain controllers the tools can use to connect to and populate the Active Directory database (NTDS) in the console. On the opposite side, Local Procedure Call is used if the connection needs to be made with the “DNS Server” service running on the local computer. Remote Procedure Call (RPC) is initiated when connecting to the “DNS Server” service on the remote computer. There are several other steps performed as part of these operations which are explained a little later.īased in the TCP/IP configuration on the local machine, an active directory tool will use one of two calls RPC or LPC. Any active directory tool written must initiate two operations (1) connecting to a DNS Server to get a list domain controllers and (2) connecting to a domain controller from the list to populate the NTDS database information in the consoles. In a nutshell, the query to find an available domain controller is sent to the DNS Server which is configured in the TCP/IP property of the local machine. The above mentioned active directory tools, when opened, will try to contact an available domain controller for fetching Active Directory database (NTDS.DIT) and displaying the database information in the tool’s console. Domain Controller Diagnostic tools such as DCDiag, Repadmin, etc.All Active Directory DS Tools (DSQuery, DSMod, DSGet, DSAdd, and so on).The following active directory tools will throw this error message: I’ll explain this process in this blog post. What you may not know is, there is a process which active directory tools or utility have to follow to contact a domain controller to get the naming information for an active directory domain. And also, there’s nothing in the event logs to let you know more about the error so you can troubleshoot the issue. The error does not provide more information as to what “Naming Information” the tool is referring to. Sometimes when you open an Active Directory tool, you might get hit with the “ Active Directory Naming Information Could Not Be Located” error message. Active Directory Naming Information Could Not Be Located Because.