Network Level Authentication (NLA) for RDP: what it is and how to turn it on
Network Level Authentication makes Remote Desktop check your password before Windows creates a session. Keep it on. Here is how to check it, turn it on three ways, and fix the sign-in errors it can cause.
Key takeaways
- NLA checks your user name and password before Windows creates a Remote Desktop session. Microsoft recommends keeping it on and turning it off only for a short time, for a client that cannot use it.
- Check it on the Remote tab of System Properties (
sysdm.cpl), or readUserAuthenticationRequiredfrom theWin32_TSGeneralSettingWMI class in PowerShell: 1 means on. - NLA is not two-step sign-in and does not stop password guessing. Pair it with an account lockout policy, long unique passwords and a firewall rule that limits who can reach Remote Desktop.
- Most NLA errors have a direct fix: let the client use CredSSP again (a saved .rdp file can turn it off), update an old client, install the CredSSP updates on the server and restart it, or change an expired password another way.
On this page
- What is Network Level Authentication?
- What does NLA protect against, and what doesn't it?
- How do I check whether NLA is on?
- How do I turn on NLA on Windows Server?
- "The remote computer requires Network Level Authentication": how do I fix it?
- Should I disable Network Level Authentication?
- NLA and CredSSP errors: what each message means
- Keep it on: do it yourself, or have us do it
What is Network Level Authentication?
Network Level Authentication (NLA) is a Remote Desktop setting that makes you prove who you are before Windows creates a remote session. Your client sends your user name and password through CredSSP (the Credential Security Support Provider) first, and only when they are valid does the server start a session and show the desktop. Should you turn it on for your Windows server? Yes: Microsoft recommends NLA for most environments and says to turn it off only temporarily, for older clients that cannot use it.
Without NLA, the server starts a session for every connection, shows the Windows sign-in screen, and only then checks the password. With NLA the check comes first, so a visitor without a valid account never gets a session.
| NLA on | NLA off | |
|---|---|---|
| When the password is checked | Before a session exists: the client sends it through CredSSP and the server checks it | On the Windows sign-in screen, inside a session the server has already started |
| What a visitor without a valid account reaches | The authentication step only | A session with a sign-in screen |
| Server resources per connection attempt | Few | A full session |
| BlueKeep (CVE-2019-0708), which affected Windows Server 2008 R2 and older | Partly mitigated, according to Microsoft | Exposed until patched |
| Password guessing | Still possible | Still possible |
| An expired password | Refused: change it another way | The sign-in screen can ask for a new one |
| Clients older than Remote Desktop Connection 6.0 | Cannot connect | Can connect |
What does NLA protect against, and what doesn't it?
What it does:
- Saves the server's resources. Microsoft's NLA documentation says the server uses few resources before the user is authenticated, which reduces the risk of denial-of-service attacks.
- Partly mitigated BlueKeep. For BlueKeep (CVE-2019-0708), a Remote Desktop flaw that needed no sign-in, the Microsoft Security Response Center called NLA a partial mitigation, because NLA requires authentication before the flaw can be triggered. An attacker with valid credentials could still exploit it, so installing updates stayed the real fix. BlueKeep affected Windows 7, Windows Server 2008 R2 and older; Microsoft says Windows 8 and Windows 10 were not affected.
What it does not do:
- It does not stop password guessing. Anyone who can reach the Remote Desktop port can still try passwords. Where failed sign-ins are audited, each one is logged as Event ID 4625; our Event ID 4625 guide shows how to read them.
- It is not two-step sign-in. NLA checks the same password, earlier. A second factor needs a multi-factor authentication (MFA) service.
- It does not help when a password is stolen. A valid user name and password pass NLA.
- It does not close or hide the port. Remote Desktop still listens on its port; see the RDP port 3389 guide.
An account lockout policy, long unique passwords and a firewall rule that limits who can reach Remote Desktop reduce the risk of brute-force sign-ins. Our RDP hardening checklist puts them in order.
How do I check whether NLA is on?
Run these on the server, as Administrator.
-
System Properties. Run
sysdm.cpland open the Remote tab. NLA is on when Allow connections only from computers running Remote Desktop with Network Level Authentication is ticked. If the box is ticked and greyed out, a Group Policy setting enforces it. -
PowerShell. The
Win32_TSGeneralSettingWMI class shows the setting and where it comes from:Get-CimInstance -Namespace root\cimv2\TerminalServices -ClassName Win32_TSGeneralSetting -Filter "TerminalName='RDP-Tcp'" | Select-Object TerminalName, UserAuthenticationRequired, PolicySourceUserAuthenticationRequiredUserAuthenticationRequiredis 1 when NLA is required and 0 when it is not.PolicySourceUserAuthenticationRequiredsays who set it: 0 the server's own setting, 1 Group Policy, 2 the default. -
Registry. The listener's own value:
Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication1 means on. A Group Policy value of the same name under
HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Servicestakes precedence over it.
Is NLA on by default? Microsoft's Group Policy reference says that when the policy is not configured, the server's own setting applies, and that NLA is enforced by default on Windows Server 2012 and Windows 8. A server image, a script or an earlier administrator can turn it off, so check rather than assume.
How do I turn on NLA on Windows Server?
Before you enable Network Level Authentication, keep your current Remote Desktop session open, and make sure every computer that connects has a client that supports NLA: Microsoft recommends updating the clients first. If you do lock yourself out, the server's console at your hosting provider, where your provider offers one, shows the screen in your browser without Remote Desktop. On a RyzenRDP server, open a Technical support ticket and we help you back in.
With System Properties
Run sysdm.cpl, open the Remote tab, choose Allow remote connections to this computer, tick Allow
connections only from computers running Remote Desktop with Network Level Authentication, and select OK.
With Group Policy
Open gpedit.msc and go to Computer Configuration > Administrative Templates > Windows Components > Remote
Desktop Services > Remote Desktop Session Host > Security. Set Require user authentication for remote
connections by using Network Level Authentication to Enabled, then run gpupdate /force. The policy takes
precedence over the System Properties checkbox. On servers in a domain, set it in a Group Policy Object instead.
With PowerShell or the registry
The WMI method SetUserAuthenticationRequired turns NLA on with 1 and off with 0:
$ts = Get-CimInstance -Namespace root\cimv2\TerminalServices -ClassName Win32_TSGeneralSetting -Filter "TerminalName='RDP-Tcp'"
Invoke-CimMethod -InputObject $ts -MethodName SetUserAuthenticationRequired -Arguments @{ UserAuthenticationRequired = [uint32]1 }
A ReturnValue of 0 means it worked. Microsoft's Azure troubleshooting article sets the same thing in the
registry from a command prompt, then restarts the machine:
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v UserAuthentication /t REG_DWORD /d 1 /f
Whichever way you choose, test with a new connection before you close the session you are in.
"The remote computer requires Network Level Authentication": how do I fix it?
The full message, "The remote computer requires Network Level Authentication, which your computer does not support", means the server insists on NLA and your client cannot do it. Most often the client is the problem. Microsoft lists what NLA needs from a client: Remote Desktop Connection 6.0 or later, on an operating system that supports CredSSP. To see whether a Windows client qualifies, open Remote Desktop Connection, select the icon in the top-left corner of its window, then About, and look for Network Level Authentication supported.
- Check the saved connection. If you connect with an .rdp file, open it in Notepad. The line
enablecredsspsupport:i:0tells the client not to use CredSSP, which NLA needs. Change it toenablecredsspsupport:i:1or delete the line (Microsoft Learn: Supported RDP properties). - Update the client. On Windows, install the pending Windows updates. On a Mac, use Windows App
(how to connect from a Mac). On Linux, use a current FreeRDP
(
xfreerdp); its manual lists NLA protocol security as on by default. - If the message adds that your domain controller cannot be contacted, the server cannot reach its domain controller. Microsoft notes that a local administrator account can still sign in; use it, then fix the domain link.
- If the client cannot be updated, turn NLA off on the server for as short a time as you can, from the server's console at your hosting provider, as the next section describes.
Should I disable Network Level Authentication?
Only for a short time, for a reason you can name. Microsoft says to keep NLA enabled whenever possible and to turn it off temporarily only for a device or client that cannot use it; its troubleshooting articles call turning it off a workaround that reduces security. NLA is a setting of the server's Remote Desktop listener, not of one connection: while it is off, it is off for every connection.
To disable NLA temporarily, work from the server's console at your hosting provider if you cannot sign in over Remote Desktop, because a client that cannot do NLA cannot reach the desktop to change the setting.
-
Limit the Remote Desktop firewall rules to your own IP address first, so the server is not open to everyone while NLA is off. Windows keeps them in the firewall group Remote Desktop; put your own address in place of the example:
Set-NetFirewallRule -DisplayGroup 'Remote Desktop' -RemoteAddress 198.51.100.7If you moved the port with a firewall rule of your own, limit that rule too. Our hardening checklist shows how to limit Remote Desktop to your IP addresses.
-
Turn NLA off in one of these ways:
-
Untick the NLA box on the Remote tab of
sysdm.cpl. -
Run the two PowerShell lines from With PowerShell or the registry above, with
[uint32]0in place of[uint32]1. -
Run Microsoft's registry command with 0, then restart the server:
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v UserAuthentication /t REG_DWORD /d 0 /f
If a Group Policy enforces NLA (the box is ticked and greyed out), set that policy to Disabled instead: a policy value overrides the other three.
-
-
Connect, fix what needed fixing, and enable Network Level Authentication again the same day, the same way you turned it off.
Do not turn NLA off to get past an expired password or a CredSSP error: both have a direct fix, below.
NLA and CredSSP errors: what each message means
| What the client says | What it means | What to do |
|---|---|---|
| "The remote computer requires Network Level Authentication, which your computer does not support" | Your client cannot do NLA, or is set not to use CredSSP | Check the saved .rdp file, then update the client (see above) |
| "An authentication error has occurred ... This could be due to CredSSP encryption oracle remediation" | One side is missing the 2018 CredSSP updates, usually the server | Update and restart both sides |
| "The Local Security Authority cannot be contacted", with a hint about an expired password | The password has expired, or must be changed at the next sign-in | Change the password another way |
| "...requires Network Level Authentication (NLA), but your Windows domain controller cannot be contacted" | A server in a domain cannot reach its domain controller | Sign in with a local administrator account, then fix the domain link |
| "The system administrator has restricted the type of logon (network or interactive) that you may use" | The account is not in Remote Desktop Users, or that group lacks the right Access this computer from the network | Add the account to Remote Desktop Users, or restore the user right |
CredSSP encryption oracle remediation
NLA runs on CredSSP. Microsoft's CredSSP updates of March to May 2018 (CVE-2018-0886) added a policy, Encryption Oracle Remediation, and the May 2018 update made Mitigated the default. Since then an updated client refuses a server that lacks the updates, or has them but has not restarted.
The fix is to update and restart both sides. If you cannot reach the server over Remote Desktop, open its
console at your hosting provider, run Windows Update there and restart. Microsoft also lists a stopgap on the
client: the policy under Computer Configuration > Administrative Templates > System > Credentials Delegation > Encryption
Oracle Remediation (registry value AllowEncryptionOracle under
HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters: 0 Force Updated Clients,
1 Mitigated, 2 Vulnerable). Microsoft notes that any change to this setting needs a restart of the computer you
change it on, both when you set it and when you set it back. Setting it to Vulnerable exposes the servers you
connect to, so use it only until the server is updated, then set it back.
Force Updated Clients does not help a client reach an old server: toward servers it behaves like Mitigated. What it adds is that a computer set to it also refuses clients that lack the updates, so set it on a server only once every computer that connects to it has them. Microsoft says not to deploy it until every client and remote host it works with supports the updated CredSSP (KB 4093492).
Expired passwords
Microsoft states that with NLA, a remote session cannot start with an expired password at all: the password is checked before the sign-in screen that would let you change it. Change it another way: from another administrator's session, or through the server's console at your hosting provider. On a RyzenRDP server, Reset password on the Server tab of your console sets a new password, which works after the server's next restart (where to find your login details).
Keep it on: do it yourself, or have us do it
Everything in this guide can be done by hand. The free RDP Security Check, a PowerShell script you run on your own server, reads your Remote Desktop settings, changes nothing, and lists what leaves room for brute-force sign-ins, NLA included. If you would rather have it done:
- Hardened Start, $9 one-time, is an option when you deploy a Windows server at RyzenRDP, and it is not ticked for you. Once the server is ready we turn NLA on, set an account lockout policy, TLS and high encryption for Remote Desktop, turn SMBv1 off, check Microsoft Defender and the Windows firewall, turn sign-in auditing on and post a short report. Remote Desktop stays on port 3389, open to every address.
- RDP Lockdown Standard, $79 one-off, applies the same settings to a server you already have, at RyzenRDP or at another provider, running Windows Server 2019, 2022 or 2025. It adds a review of administrator accounts, limits Remote Desktop to your IP addresses if you want that, and ends with a before-and-after report. RDP Lockdown Plus, $149, adds two-step sign-in on an MFA account of your own.
- RDP Rescue: if a CredSSP error on the server, or an expired password that NLA blocks, keeps you out of a RyzenRDP server, we fix the server side as one listed fix at $39, invoiced only once you can sign in again, and keep NLA on. If your own computer needs an update, we tell you. A fault on our side is fixed free.
Hardened Start and RDP Lockdown reduce the risk of brute-force sign-ins; neither can make a server impossible to break into, so keep Windows updated either way. See what RDP Lockdown changes, or the RDP Rescue fix list.
A RyzenRDP Windows VPS gives you full Administrator access, so every step above is yours to run. The Windows Server license is not included in the plan price: Windows Server is installed for you but not activated, and you license and activate it yourself. The server is set up instantly once your payment is confirmed, and plans start at $14.99 a month.
FAQ
Is Network Level Authentication on by default on Windows Server?
Microsoft's Group Policy reference says NLA is enforced by default on Windows Server 2012 and Windows 8 when no policy sets it. A server image, a script or an earlier administrator can still turn it off, so check it on your own server. Open System Properties with sysdm.cpl and look at the Remote tab, or read UserAuthenticationRequired from the Win32_TSGeneralSetting WMI class in PowerShell, where 1 means NLA is required.
Does NLA stop brute-force attacks?
No. NLA checks the password before Windows creates a session, so each attempt costs the server less work, but anyone who can reach the Remote Desktop port can still try passwords. An account lockout policy, long unique passwords and a firewall rule that limits who can reach the port reduce the risk of brute-force sign-ins.
Is NLA the same as two-factor authentication?
No. NLA checks the same user name and password, only earlier in the connection. Two-step sign-in adds a second factor, such as a prompt on your phone, and needs a multi-factor authentication service with a Windows sign-in agent, for example Cisco Duo.
Can I connect from a Mac or Linux with NLA on?
Yes. Windows App, Microsoft's Remote Desktop client for the Mac (formerly Microsoft Remote Desktop), works with NLA, and FreeRDP on Linux has NLA on by default according to its manual. The clients that fail are very old ones that cannot use CredSSP, the protocol NLA runs on, or a client set not to use it.
Why can't I sign in with an expired password when NLA is on?
With NLA, the password is checked before Windows shows the sign-in screen that would let you change it, so Microsoft notes that a session cannot start with an expired password. The client usually says the Local Security Authority cannot be contacted and that this could be due to an expired password. Change the password another way, from another administrator's session or through the server's console at your hosting provider, rather than turning NLA off.
Should I turn off NLA to fix a connection error?
Usually not. Most NLA errors have a direct fix, such as setting a saved .rdp file back to use CredSSP, updating an old client, installing the CredSSP updates on the server and restarting it, or changing an expired password another way. NLA is a server setting, so turning it off affects every connection, not one session. Turn it off only for a short time when a client cannot be updated, limit Remote Desktop to your own IP address while it is off, and turn it back on the same day.
Sources
- Microsoft Learn: Enable Remote Desktop on your PC (why to allow connections only with NLA; ms.date 18 June 2025)
- Microsoft Learn: ADMX_TerminalServer Policy CSP (TS_USER_AUTHENTICATION_POLICY: the policy name, path, registry value and default)
- Microsoft Learn (archived, Windows Server 2008 R2): Configure Network Level Authentication for Remote Desktop Services Connections (the checkbox, Group Policy precedence, client requirements, the About check)
- Microsoft Learn: Win32_TSGeneralSetting class and SetUserAuthenticationRequired method
- Microsoft Learn: Troubleshoot authentication errors when you use RDP to connect to Azure VM (the RDP-Tcp UserAuthentication value; the domain controller message)
- Microsoft Learn: User can't authenticate or must authenticate twice (CredSSP encryption oracle remediation; restricted type of logon)
- Microsoft Support: CredSSP updates for CVE-2018-0886 (KB 4093492, Encryption Oracle Remediation)
- Microsoft Learn: Password change for expired password failing (KB 2879424, expired passwords with NLA)
- Microsoft Security Response Center: Prevent a worm by updating Remote Desktop Services (CVE-2019-0708) (14 May 2019)
- Microsoft Learn (archived): What's new in the Remote Desktop client for macOS (NLA and expired passwords on the Mac client)
- Microsoft Learn: Supported RDP properties (enablecredsspsupport: with 0, RDP does not use CredSSP; ms.date 11 August 2026)
- FreeRDP: xfreerdp manual page (Ubuntu 24.04, FreeRDP 2.11.5: NLA protocol security on by default)
- SecureW2 blog: "What is Network Level Authentication: what it does and doesn't do" (securew2.com, 23 April 2026)