Which authentication error do you have?

An RDP authentication error is frustrating precisely because you can reach the server — the connection works, the login screen appears, and then the door stays shut. The fix depends entirely on which error you see, because "authentication failed" is a family of problems, not one problem. Read the exact message before doing anything; this guide is organized so you can jump straight to yours.

The family splits into four groups: credential errors ("logon attempt failed," "username or password incorrect") — the server doesn't believe you are who you claim; account-state errors ("account locked out," "account disabled," "password expired") — the credentials are right but the account can't log in; handshake errors ("an authentication error has occurred," CredSSP messages) — the security negotiation itself failed; and the sneaky one, clock drift, which disguises itself as several of the above. Each group has different fixes, and applying the wrong group's fix wastes your afternoon.

What does the error say? Wrong password / logon failed Credential fixes Locked out / disabled Account fixes Authentication error / CredSSP Handshake fixes Weird / intermittent Check the clock
Fig. 1 — Sort your error into one of four groups; each has its own fixes.

Fixes for credential errors (the common ones)

"The logon attempt failed" and "the username or password is incorrect" mean exactly what they say — but the cause often isn't a wrong password:

  • Retype, don't paste. Password managers and copy-paste can smuggle in a trailing space. Type the password manually once, slowly. This resolves a surprising share of "I'm sure it's right" cases.
  • Clear saved credentials. Open Credential Manager → Windows Credentials, delete the saved entry for the server, and enter credentials fresh. Stale saved credentials (from before a password change) fail with misleading messages — and they fail before your typed ones get a chance.
  • Check the username format. Some servers want Administrator, others want .\Administrator or SERVERNAME\user. If your provider's welcome email shows a specific format, use exactly that. Domain-joined servers need the domain prefix; standalone servers usually don't.
  • Caps Lock and keyboard layout. Check both. Remote sessions can also apply a different keyboard layout than your local one — if your password contains symbols, verify each types as expected in the username field first (where you can see it).
  • Confirm the password actually changed. If you recently changed it, make sure the change completed (change it once more deliberately). If someone else administers the server, ask whether the password was reset without telling you.

Fixes for locked-out and disabled accounts

These errors mean the credentials are fine but the account itself can't log in:

  • "Account locked out." Too many failed attempts triggered the lockout policy. Wait out the lockout duration (commonly 30 minutes) without attempting — every attempt during lockout can reset the timer. Then log in carefully once. If it recurs, something is hammering the account (a saved wrong password somewhere retrying, or an actual brute-force attempt — see our brute-force protection guide).
  • "Account disabled." The account was disabled — by an administrator, by a billing suspension, or by a policy. Check the client area for service status first (suspensions disable access), then contact whoever administers the server.
  • "Password expired" / "must change password." The password aged out. If you can reach the password-change screen, change it there; if you're locked at the RDP prompt with no way to change it, you'll need the provider or admin to reset it — this is a two-minute support task, not a server rebuild.
  • "User not in Remote Desktop Users." The account exists and the password is right, but it lacks permission to log in via RDP. An administrator must add it to the Remote Desktop Users group (or Administrators). New manually-created accounts hit this constantly.

Don't brute-force yourself: repeatedly guessing at a login triggers lockout policies and looks exactly like an attack. After three careful attempts, stop and verify the credentials through another channel (welcome email, password manager, provider) instead of trying a fourth.

Fixes for NLA and security-handshake errors

"An authentication error has occurred" (without "logon failed") means the handshake broke, not your password. The usual suspects:

  • Update the RDP client. Network Level Authentication (NLA) requires a reasonably modern client. Update to the latest Microsoft Remote Desktop client — free — and retry. Ancient clients (or third-party ones) against NLA-enforcing servers fail here.
  • CredSSP mismatch. If the message mentions CredSSP or "encryption oracle," that's a specific patch-mismatch problem with its own fix — see our CredSSP error guide rather than guessing.
  • TLS/Security layer mismatch. If the server was recently hardened (TLS 1.2+ enforced, old protocols disabled) and your client is old, the handshake dies. Updating the client fixes it; the server side is correctly configured and shouldn't be loosened.
  • Don't disable NLA as a "fix." You'll find advice to turn off NLA on the server to make old clients connect. Don't — NLA is a meaningful security layer, and disabling it to accommodate one outdated client weakens every login. Update the client instead.
Your computer: correct time Server: 25 minutes fast ✗ Clock drift silently breaks authentication
Fig. 2 — If client and server clocks disagree by more than a few minutes, security handshakes fail.

The silent killer: clock drift

Here's the one nobody suspects: if the server's clock (or yours) is off by more than about five minutes, authentication handshakes fail — sometimes with misleading "logon failed" messages. Kerberos and TLS both embed timestamps, and skewed clocks make valid credentials look invalid or expired.

The fix is boring and total: make sure both ends sync time automatically. On your computer, that's the "set time automatically" toggle. On the server (if you have admin access), verify the Windows Time service is running and syncing — a server that's been snapshotted, restored, or long-neglected can drift badly. If you can't reach the server at all, mention clock sync to support; it's a 30-second check on their end and it resolves a whole class of "impossible" login failures.

This is worth checking early when the error is weird or intermittent — credentials that "sometimes work" are a classic clock-drift signature, because drift crosses the tolerance threshold and drifts back.

Error message decoder table

Error messageGroupFix first
"The logon attempt failed"CredentialsClear saved creds, retype manually, check username format
"The referenced account is locked out"Account stateWait out lockout; stop retrying; check for stale saved passwords
"The account is disabled"Account stateCheck service status; contact admin/provider
"Password expired / must be changed"Account stateChange at prompt, or ask admin for a reset
"An authentication error has occurred" (CredSSP)HandshakeCredSSP guide
"An authentication error has occurred" (NLA)HandshakeUpdate RDP client; don't disable NLA
Intermittent / "sometimes works"Clock driftVerify time sync on both ends

RDP Authentication Error: FAQ

Usually it's not the password you think: stale saved credentials in Credential Manager take precedence over what you type, the username format may be wrong (try .\Administrator), or a trailing space snuck in via paste. Clear saved credentials and type everything manually once before assuming the password itself is wrong.

It depends on the server's lockout policy — 30 minutes is common, but it varies. Crucially, don't keep trying during the lockout: each attempt can reset the timer. Wait it out fully, then log in carefully once with verified credentials.

Yes. Authentication protocols embed timestamps, and if the client and server clocks differ by more than a few minutes, valid credentials get rejected — sometimes with misleading error messages. Enable automatic time sync on both ends; it's a 30-second fix for a baffling class of failures.

No. Disabling NLA weakens security for every login just to accommodate (usually) an outdated client. Update your RDP client to the latest version instead — NLA handshake failures are a client-age problem far more often than a server misconfiguration.

New accounts aren't in the Remote Desktop Users group by default. An administrator needs to add the account to that group (Computer Management → Local Users and Groups → Groups → Remote Desktop Users). The password can be perfect and login still fails without this membership.

A connection error means you never reached the server (network path problem — see our RDP not connecting guide). An authentication error means you reached it fine but the login was rejected — wrong credentials, locked account, or a failed security handshake. The distinction tells you which guide to follow.

Ready for your own RDP server?

Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan. Pay by credit/debit card, bank transfer, Bitcoin or altcoins.

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

3-day money-back guarantee · Instant setup · 30+ server locations · 99% uptime SLA