大网数据广告活动
账户与安全

Troubleshoot domain controller location issues in Windows

· 52CE 我爱测

Helps troubleshoot domain controller location issues in Windows.

This article helps troubleshoot domain controller location issues in Windows.

Domain controller (DC) location, also known as DC Locator, refers to the algorithm the client machine uses to find a suitable domain controller. DC Locator is a critical baseline functionality in all enterprise environments. For more information about how domain controllers are located in Windows, see Locating domain controllers in Windows and Windows Server.

If DC Locator doesn't work as expected in Active Directory domains, troubleshoot issues by using the following steps:

Note: Authentication is the first step in almost all functional scenarios in an Active Directory enterprise environment. However, authentication occurs after the client communicates with an Active Directory domain controller.

  1. Check the system logs (for example, the event source is NETLOGON) on both the client and the server. Also check the Directory Service logs (for example, the event source is NTDS KCC) on the server and Domain Name System (DNS) logs on the DNS server.

  2. Open an elevated command prompt, and check the IP configuration by running the following command:

    ipconfig /all
    
  3. Use the Ping utility to verify network connectivity and the name resolution. Ping the IP address, the server name, and the domain name.

  4. Use the PortQryUI tool to probe for availability of important domain controller services. When you start the tool, specify the domain controller fully qualified domain name (FQDN), and query the Domains and Trusts set of services as follows:

    :::image type="content" source="media/troubleshoot-domain-controller-location-issues/port-query-udp-389.png" alt-text="Screenshot of the Port Query tool window showing the query result with UDP port 389.":::

    The screenshot shows one important port for DC discovery which is UDP/389, and in this case, it is successful.

    [!NOTE] UDP/389: This port is required to discover AD services.

  5. Use the nslookup tool to verify that DNS entries are correctly registered in DNS. Verify that the server host records and the globally unique identifier (GUID) SRV records can be resolved.

    For example, to verify record registrations, run the following commands:

    nslookup servername.childofrootdomain.rootdomain.com
    
    nslookup guid._msdcs.rootdomain.com
    

    If either of these commands doesn't succeed, use one of the following methods to reregister records with DNS:

    • To force the host record registration, use the ipconfig /registerdns command.
    • To force the domain controller service registration, stop and restart the Netlogon service.
    • To detect domain controller issues, run the DCdiag utility from a command prompt. The utility runs many tests to verify that a domain controller is running correctly. Use the dcdiag /v >dcdiag.txt command to send the results to a text file.
  6. Use the Ldp.exe tool to connect and bind to the domain controller to verify appropriate Lightweight Directory Access Protocol (LDAP) connectivity.

  7. If you suspect that a particular domain controller has issues, turn on Netlogon debug logging. Use the Nltest tool by running the nltest /dbflag:0x2000ffff command. The information is then logged in the Netlogon.log file under the %windir%\Debug folder.

  8. If you still haven't isolated the issue, use network monitor tools like Wireshark to capture and analyze network traffic between the client and the domain controller.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。