You start a Remote Desktop connection and get a message such as “The remote computer requires Network Level Authentication, which your computer does not support,” or “An authentication error has occurred.” The connection stops before you even see the sign-in screen. When PAGODA 127 a Windows 10 Remote Desktop Network Level Authentication error appears, the two computers cannot complete the security check that happens before the session starts.
Network Level Authentication, or NLA, asks for your credentials before a full remote session opens. That protects the remote PC from attacks, but it requires both computers to support the same security methods and to reach the domain controller on work networks.
Errors usually appear when one PC is outdated, when the remote PC’s clock is wrong, when security protocols differ after updates, or when the account cannot be verified.
Updating both systems and checking the account resolves most NLA errors without lowering security.
What Usually Triggers It
NLA errors appear for these reasons:
- One computer is missing security updates.
- The account cannot be verified, for example because the password changed.
- The clock on one PC is wrong, which breaks authentication.
- A domain-joined PC cannot reach its domain controller.
Older Remote Desktop clients on very old systems may not support NLA at all.
First Steps to Try
Fix the basics on both PCs.
- Install all Windows updates on both computers and restart them.
- Check that the date, time, and time zone are correct on both.
- Sign in once locally on the remote PC with the account password to refresh credentials.
- Use the account’s password, not a PIN, when connecting.
- Try connecting by IP address instead of computer name.
If the Problem Continues
Check remote settings and certificates.
- On the remote PC, open Settings > System > Remote Desktop and confirm it is enabled and your account is allowed.
- Make sure the Remote Desktop Services service is running on the remote PC.
- On work networks, ask IT whether the PC has lost its trust relationship with the domain.
- Clear old saved credentials for that PC in Credential Manager on your computer.
- As a short test only, an administrator can untick “Require computers to use Network Level Authentication” in Remote Desktop’s advanced settings, then turn it back on.
Protect Your Data First
Do not leave NLA disabled; it is an important defence against attacks on Remote Desktop. Never expose Remote Desktop directly to the internet without a VPN or gateway.
The Bottom Line
NLA errors mean the pre-connection security check failed. Update both PCs, fix the clocks, use the account password, clear old credentials, and keep NLA enabled once the problem is solved.
