Quick answer: On the server, open System Properties > Remote tab and check "Allow connections only from computers running Remote Desktop with Network Level Authentication." Every modern client — Windows, Mac, Android, iPhone, Remmina, FreeRDP — supports NLA, so enabling it rarely breaks legitimate access. It stops unauthenticated users from ever reaching the login screen.

What NLA actually does

To understand NLA, picture the two ways a remote connection can begin. Without NLA, the server accepts the connection, allocates session resources, renders the full Windows login screen, and then asks who you are. An attacker gets a login prompt to hammer, and the server burns memory and CPU on every attempt — including the thousands of automated ones from our brute force discussion.

With NLA, the order flips: the client must authenticate first, using the CredSSP protocol, before the server creates any session. No valid credentials, no session, no login screen — the connection is refused at the gate. This kills two birds: it denies attackers the interactive login surface, and it protects the server from resource-exhaustion attacks that flood it with half-open sessions. It also enables single sign-on niceties in domain environments, where your Windows login flows straight through.

Think of it as the difference between a building with an unlocked lobby (anyone can walk in and try office doors) and one with a badge reader at the entrance (no badge, no lobby). The offices still have their own locks — NLA does not replace passwords — but the attack surface shrinks dramatically.

Without NLA 1. Session created 2. Login screen shown 3. Attacker guesses here With NLA 1. Credentials verified 2. Session created 3. Desktop appears NLA moves authentication ahead of session creation.
Fig. 1 — NLA authenticates before the server spends anything on the session.

Require NLA on the server

On the server, right-click This PC > Properties > Remote settings (or run SystemPropertiesRemote.exe), and on the Remote tab check "Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)." Click OK. That single checkbox is the entire server-side change — no reboot needed, and it takes effect for new connections immediately.

For Group Policy control across machines, the setting lives at Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security: "Require user authentication for remote connections by using Network Level Authentication." Enabled means NLA is mandatory; this is how administrators enforce it fleet-wide so nobody can quietly uncheck the box.

There is also a registry path for scripting: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp, value UserAuthentication — 1 requires NLA, 0 allows non-NLA connections. Useful in setup scripts, but the GUI checkbox sets exactly this value, so prefer the GUI unless you are automating. All of this needs administrator rights, which is standard on plans with full admin RDP access.

Client compatibility

The historical reason people hesitated on NLA was old clients — Windows XP-era RDP clients could not do it. That era is over. Every current client supports NLA: the built-in Windows client, the Mac App Store client (see our Mac setup guide), the Android and iPhone apps (see the Android and iPhone guides), Remmina and FreeRDP on Linux (see Linux clients), and every credible connection manager.

On the Windows client there is one related setting to know: in the .rdp file or GUI, enablecredsspsupport:i:1 means the client will attempt CredSSP/NLA. It defaults to on, so you will only ever touch it if something turned it off. If you manage a museum of ancient clients, keep one non-NLA fallback path — but for any server on the modern internet, requiring NLA is the safe default.

ClientNLA supportNotes
Windows Remote Desktop ConnectionYesDefault on; the reference implementation
Microsoft Remote Desktop (Mac)YesWorks with NLA-required servers out of the box
Remote Desktop (Android)YesEnable in the PC entry if ever disabled
Remote Desktop Mobile (iPhone)YesNo extra configuration needed
Remmina / FreeRDP (Linux)YesUpdate the client rather than disabling NLA server-side
mRemoteNG, RDM, Royal TSYesAll modern managers negotiate NLA
✓ No anonymous sessions Less resource abuse All modern clients OK One checkbox, three wins.
Fig. 2 — What the NLA checkbox buys you.

Fixing NLA errors

The classic error — "The remote computer requires Network Level Authentication, which your computer does not support" — means exactly what it says: the client is too old or has CredSSP disabled. Fix the client, not the server: update the RDP client to a current version, and on Windows ensure the Credential Security Support Provider is intact (it is part of Windows; third-party "debloating" tools sometimes damage it).

A trickier variant involves CredSSP encryption oracle errors after Windows updates: client and server disagree on CredSSP patch levels. The real fix is updating both sides — the error is the protocol refusing to downgrade to a vulnerable version, which is it doing its job. Workarounds that disable the check weaken security; patch instead.

If you genuinely must connect from an ancient client once, the server checkbox can be temporarily unchecked — but treat that as emergency surgery with a plan to re-enable it, not a configuration. Every hour NLA is off, the login screen is back in the lobby.

What NLA does not do

NLA is authentication gating, not a complete security strategy. It does not make weak passwords strong — pair it with the brute force defenses (lockout policy, renamed Administrator, long passwords). It does not encrypt anything beyond what RDP already encrypts — for the encryption layer, see our RDP TLS encryption guide. It does not add a second factor — that is two-factor authentication. And it does not hide the port — combine it with a nonstandard port or, better, VPN-only access for the full stack.

The right mental model: NLA is the lock on the building's front door. You still need good locks on the office doors (passwords), an alarm (lockout policy), and ideally a gated compound (VPN/firewall). The security best practices checklist assembles the whole stack in one place.

Enable NLA: step by step

  1. Inventory your clients. Confirm every device you connect from runs a current RDP client (anything from the last decade qualifies).
  2. Open Remote settings on the server: This PC > Properties > Remote settings, or run SystemPropertiesRemote.exe.
  3. Check the NLA box: "Allow connections only from computers running Remote Desktop with Network Level Authentication."
  4. Click OK — no reboot needed; new connections must authenticate first from now on.
  5. Test from each client — Windows, Mac, phone — to confirm they all negotiate NLA cleanly.
  6. For fleets, enforce via Group Policy so the setting cannot drift back off.
  7. Layer the rest: lockout policy, strong passwords, and firewall scoping from the brute force guide.

Need an RDP server that just works?

Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan.

Shared Servers$6/mo
Dedicated Server$165/mo
Get Started

3-day money-back guarantee · Dedicated IP on every plan · 24/7 support

RDP Network Level Authentication: FAQ

NLA requires the connecting user to authenticate before the server creates a remote session. Without it, anyone can reach the Windows login screen; with it, unauthenticated connections are refused up front, which also protects the server from resource-exhaustion attacks.

Open System Properties, Remote tab (run SystemPropertiesRemote.exe), and check Allow connections only from computers running Remote Desktop with Network Level Authentication. It applies immediately to new connections with no reboot.

Yes — they solve different problems. A strong password resists guessing; NLA denies attackers the login screen entirely and stops them consuming server resources with unauthenticated sessions. Use both.

The client is outdated or its CredSSP support is damaged. Update to a current RDP client rather than disabling NLA on the server — every modern client on Windows, Mac, Android, iOS, and Linux supports it.

It means the client and server have mismatched CredSSP security updates and the protocol is refusing an unsafe downgrade. Update both sides instead of working around the check, which would weaken security.

No. NLA is one strong layer: combine it with account lockout, long unique passwords, a renamed Administrator account, firewall IP restrictions, and ideally VPN-only access for complete protection.