Windows Server: Enable Network Level Authentication (NLA) on RDP
Network Level Authentication makes a client prove the user's credentials before Windows builds a Remote Desktop session. Enable NLA with the GUI, PowerShell or Group Policy, then verify it on port 12230.
- Intermediate
- Windows VPS · Admin RDP
- 5 min read
Network Level Authentication (NLA) checks a user's credentials before Windows Server builds a full Remote Desktop session. With NLA on, an unauthenticated client never reaches the logon screen, so anonymous connections, scanner traffic and pre-auth resource use stop at the door. This guide turns NLA on for your RunRacks Windows VPS or Admin RDP — by GUI, PowerShell and Group Policy — and then confirms it works on TCP port 12230.
Before you start
- Administrator access to the server and its local or domain account credentials.
- A second way in. Open the browser console in the Dashboard and keep that tab open until you have reconnected with RDP successfully.
- A client that supports CredSSP: Windows 7 / Server 2008 R2 or later with current updates, or a current Microsoft Remote Desktop app on macOS, iOS or Android.
- Your connection details from the Dashboard: the server IP and the RDP port, which is 12230 on RunRacks Windows VPS and Admin RDP.
- Note the current RDP settings so you can compare afterwards.
Changing RDP authentication settings can lock you out if the client or account does not meet the new requirement. Keep the Dashboard console session open, and read the troubleshooting section before you apply the change.
Read the current state first. UserAuthentication = 1 means NLA is on, 0 means it is off.
$rdp = 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp'
Get-ItemProperty -Path $rdp | Select-Object UserAuthentication, SecurityLayer, PortNumberPortNumber should show 12230. If it shows 3389, check the port guide linked at the end before you continue.
Enable NLA on Windows Server RDP
Option 1: System Properties
- Run
sysdm.cpl(or open Settings, System, About, Advanced system settings). - Go to the Remote tab.
- Tick Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended).
- Click Apply, then OK.
The checkbox writes the same registry value described below, so you can use whichever route suits your workflow.
Option 2: PowerShell
This is the fastest route on a fresh VPS and the easiest to script across several servers.
$rdp = 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp'
Set-ItemProperty -Path $rdp -Name UserAuthentication -Value 1 -Type DWord
Get-ItemProperty -Path $rdp -Name UserAuthenticationThe change applies to new connections. Sessions that are already open stay connected, so a current admin session keeps running while you test.
NLA works with the default SecurityLayer value of 1 (Negotiate), which lets the client and server agree on TLS. Leave it alone unless you have a specific reason to pin the transport layer.
Option 3: Group Policy
Use this when several servers must share the setting, or when you want the configuration to survive a rebuild from a golden image.
- Run
gpedit.mscfor a local policy, or open Group Policy Management on a domain. - Navigate to Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Security.
- Open Require user authentication for remote connections by using Network Level Authentication and set it to Enabled.
- Apply the policy.
gpupdate /forceGroup Policy reasserts the value on refresh, so if someone later flips the checkbox in System Properties, the policy will put it back. Check with gpresult /h %temp%\rsop.html if the setting does not seem to take.
NLA does not replace account hygiene. Create named accounts instead of sharing one administrator login — see Create Windows users with Remote Desktop access.
Check it works
- Confirm the port is reachable from your workstation:
Test-NetConnection 203.0.113.10 -Port 12230TcpTestSucceeded : True means the network path is open.
- Connect with an explicit port:
mstsc /v:203.0.113.10:12230With NLA enabled, the credential prompt appears before the session is created. You should see the certificate confirmation (once), the username and password box, and only after a successful sign-in does the remote desktop and its logon screen appear.
- Re-read the registry value to confirm it stuck:
Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication- Review recent sessions on the server side:
Get-WinEvent -LogName 'Microsoft-Windows-TerminalServices-LocalSessionManager/Operational' -MaxEvents 10 |
Select-Object TimeCreated, Id, MessageYou should see logon and reconnect events that line up with your test connections, and nothing from addresses you do not recognise.
Troubleshooting
- "The remote computer requires Network Level Authentication, which your computer does not support" — the client is old or missing CredSSP updates. Update the client OS or app rather than switching NLA off on the server; a current Microsoft Remote Desktop build on Windows, macOS, iOS and Android all support it.
- "An authentication error has occurred. The function requested is not supported" — usually a CredSSP mismatch between an unpatched client and a patched server. Patch both sides and reboot before changing any registry workaround you find online.
- Connection drops right after you enter credentials — the account may lack the right to sign in over RDP. Add it to the local Remote Desktop Users group, or check Allow log on through Remote Desktop Services in
secpol.msc. - You cannot connect at all after the change — open the browser console in the Dashboard, set
UserAuthenticationback to0, reconnect on port 12230, and fix the client before re-enabling. - Connection attempts hit 3389 and time out — the server listens on 12230. Always connect as
IP:12230; see RunRacks RDP port 12230.
Next steps
- Secure Remote Desktop on Windows Server for the wider checklist around NLA.
- Check that Windows is listening on RDP port 12230 if connections behave strangely.
- RDP Hardening: Preventing Privilege Escalation via Group Policy to limit what a signed-in session can do.
- Connect to your Admin RDP from Windows, Mac and phone, or compare plans on the Windows VPS page.
Was this guide helpful?
Still stuck?
Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.
Related guides
Security
Check the Windows Firewall rule for RDP port 12230
Find and verify the inbound TCP 12230 rule that lets Remote Desktop reach your RunRacks server, recreate it if it was deleted and scope it without locking yourself out.
- Intermediate
- Windows VPS · Admin RDP
- 5 min read
Security
Linux Security: Using aide for File Integrity Monitoring on VPS
AIDE builds a checksum database of your system files and reports anything that changed. This guide installs it, creates a baseline, tunes the rules and schedules daily checks on a Linux VPS.
- Advanced
- Linux VPS
- 6 min read
Security
iptables basics: list, allow, drop and save rules
Learn how iptables chains and rule order work, then build a small ruleset that allows SSH and web traffic, drops everything else and can be edited by line number.
- Intermediate
- Linux VPS
- 6 min read