there are currently no logon servers available to service the logon request
This skill troubleshoots the classic there are currently no logon servers available to service the logon request error, meaning the workstation cannot find a domain controller. It guides helpdesk staff through checking the network path, DNS, and the Netlogon service before assuming a server outage. Not for trust-relationship or credential failures.
Error message
There are currently no logon servers available to service the logon request.TL;DR
The machine cannot locate any domain controller, usually because of DNS or VPN, not because every DC is down. Confirm the machine points at domain DNS servers, verify VPN or LAN connectivity, and check the Netlogon service is running. Retry the logon once name resolution works.
Steps
Verify the machine is connected to the network or VPN and note its DNS servers. Expected: You can see whether DNS points at domain controllers or a public resolver.
Test name resolution for the domain and for a known domain controller. Expected: The domain resolves to DC addresses, or you confirm DNS is wrong.
Fix the DNS assignment or reconnect the VPN, then confirm the Netlogon service is running. Expected: Name resolution succeeds and Netlogon reports running.
Have the user attempt the logon again. Expected: The logon succeeds without the error.
When to use
- The exact message appears at the Windows logon screen
- Remote workers see it after their VPN client drops
- The machine was recently moved between subnets or Wi-Fi networks
When not to use
- The message is the trust relationship failure (the machine found a DC but the account is broken)
- Cached credentials let the user in but group policy fails (partial connectivity instead)
- The user is on Entra-only join with no domain (different identity path)
Why this happens
Windows logon needs to contact a domain controller to validate credentials unless cached logons apply. DNS is the usual culprit: if the machine uses a public or stale resolver, it cannot find DC SRV records and reports no logon servers even though the DCs are healthy.
Edge cases
- Machines with cached credentials may log on fine and hide this until group policy or a password change needs a DC.
- Split-tunnel VPN configs that exclude DNS can break DC discovery while everything else looks connected.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_OyOkCwU33fqxiierulLQZA