| Previous | Next |
| STATUS_INVALID_VARIANT | STATUS_ACCOUNT_LOCKED_OUT |
STATUS_DOMAIN_CONTROLLER_NOT_FOUND
No usable controller satisfies the discovery request
Controller discovery evaluates the domain name, requested services, site, DNS SRV records, reachability, and controller response. A domain can exist while no controller currently satisfies constraints such as writable, KDC, global catalog, or site preference.
Use the same flags and credentials as the failing application when reproducing the lookup. A generic ping or successful name resolution is insufficient because DC Locator also validates service advertisements and availability.
What to inspect
- Capture the domain, site, and DsGetDcName-style flags used by the caller.
- Query the relevant _msdcs and site-specific SRV records and verify their target addresses.
- Check Netlogon discovery logs, time, firewall paths, and whether a writable or role-specific controller is required.
References
- Microsoft: Domain controller locator
- Microsoft: Verify domain-controller SRV records
- Microsoft Open Specifications: Netlogon Remote Protocol
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.