How to fix Error 1908 on Windows 11

by

Troubleshooting Guide: Error 1908 – Could Not Find the Domain Controller

Why This Error Happens

Error 1908 typically occurs when a Windows 11 client cannot properly resolve or communicate with a domain controller due to DNS misconfiguration, as the client relies on DNS SRV records to locate domain services. This can also result from network connectivity issues, incorrect network adapter DNS settings pointing to a public DNS server instead of the internal DNS server, or a mismatch in domain trust relationships caused by an outdated computer account password. Additionally, firewall rules blocking essential Active Directory ports (such as 389, 445, or 88) can prevent the handshake needed to locate the domain controller.

Step-by-Step Resolution Guide

Step 1: Verify and Correct DNS Settings

  • Open Control Panel and navigate to Network and Sharing Center, then click on your active network adapter.
  • Right-click the adapter, select Properties, then double-click Internet Protocol Version 4 (TCP/IPv4).
  • Ensure the “Preferred DNS server” field points to your internal Domain Controller’s IP address (e.g., 192.168.1.10), not a public DNS like 8.8.8.8.
  • Run ipconfig /flushdns in Command Prompt to clear any cached incorrect records.

Step 2: Check Network Connectivity to the Domain Controller

  • Open Command Prompt as Administrator and run ping [DomainControllerName] to check basic connectivity.
  • Run nltest /dsgetdc:[YourDomainName] to specifically query if the client can locate a domain controller.
  • If this fails, check physical network cables, VPN connections, or Wi-Fi stability to ensure the machine is on the correct subnet/VLAN.

Step 3: Rejoin the Device to the Domain

  • Navigate to Settings > System > About > Advanced system settings.
  • Click the Computer Name tab, select Change, and temporarily switch the PC to a Workgroup (e.g., “WORKGROUP”) to reset the machine account.
  • Restart the PC, then repeat the steps to switch back to the Domain, entering valid domain admin credentials to re-establish the trust relationship.

Step 4: Review Windows Firewall and Security Software

  • Ensure that ports 53 (DNS), 88 (Kerberos), 389 (LDAP), and 445 (SMB) are not blocked by third-party antivirus or the built-in Windows Defender Firewall.
  • Temporarily disable third-party security software to test if it is the root cause of the blocked authentication request.

Alternative or Verification Steps

  • Verify the Fix: Open Command Prompt and run gpupdate /force and nltest /sc_verify:[YourDomainName]. If these commands complete without error, the trust relationship and domain controller location are successfully restored.
  • Alternative Solution: If rejoining the domain fails, use the Active Directory Users and Computers (ADUC) console on a server to reset the specific computer account, then attempt the domain join process again on the Windows 11 client.