# Fix RDP Authentication Errors: CredSSP, NLA and Group Policy

Source: https://srvscripts.com/guides/rdp-authentication-error-credssp-nla/
Updated: 2026-11-13
Publisher: srvScripts (https://srvscripts.com/)

“An authentication error has occurred” is one of the least helpful messages Remote Desktop shows. It can mean a CredSSP version mismatch, a missing user right, clock drift or a hardening policy. On Windows 11 and Windows Server 2025 the cause is usually Group Policy. This guide maps each error to the setting behind it and fixes it without switching off Network Level Authentication (NLA).

**Short answer:** Read the full error text. If it ends with “This could be due to CredSSP encryption oracle remediation”, update and restart both machines; set Encryption Oracle Remediation to Vulnerable on the client only as a short bridge. If it says the administrator has restricted the types of logon, the account lacks Access this computer from the network or Allow log on through Remote Desktop Services, is not in Remote Desktop Users, or is listed in a Deny right. A “time or date difference” error means fixing the clock. Keep NLA on. (Reviewed November 2026.)

## Read the exact error first

Each message points to a different layer. Copy the full text before you change anything.

| Message | What it usually means |
| --- | --- |
| “An authentication error has occurred. The function requested is not supported.” followed by “This could be due to CredSSP encryption oracle remediation” | The client and server cannot agree on a CredSSP version |
| “The system administrator has restricted the types of logon (network or interactive) that you may use.” | A user right is missing or a Deny right applies |
| “The connection was denied because the user account is not authorized for remote login.” | The account is not in Remote Desktop Users and lacks the Allow right |
| “Remote Desktop cannot verify the identity of the remote computer because there is a time or date difference between your computer and the remote computer.” | Clock skew against the domain controller |
| “Account restriction is preventing this user from signing in.” | A credential protection feature such as Remote Credential Guard is blocking the logon |

## Enable RDP with NLA on Windows 11

On a single PC, open Start, Settings, System, Remote Desktop, turn Remote Desktop on and select Confirm. The remote PC must run a Pro, Enterprise or Education edition, or Windows Server. Windows Home can connect out to other machines but cannot accept incoming Remote Desktop connections. This is the usual reason RDP cannot be enabled on a Surface Go: check Settings, System, About.

NLA authenticates the user before a session is created. To enforce it across many machines, enable:

```
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
```

When it is not configured, the local setting applies. To see what the listener uses now (1 means NLA is required, 0 means it is not):

```
Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' |
  Select-Object UserAuthentication
```

For the full GPO and firewall setup, see [enable Remote Desktop with Group Policy](/guides/enable-remote-desktop-group-policy/).

## CredSSP encryption oracle remediation

NLA uses CredSSP. The 2018 updates for CVE-2018-0886 changed it, and the May 2018 update made Mitigated the default. A patched client now refuses an unpatched server, or a patched server that has not restarted. The setting is:

```
Computer Configuration\Administrative Templates\System\Credentials Delegation\
  Encryption Oracle Remediation
```

| Option | AllowEncryptionOracle | As a client | As a server |
| --- | --- | --- | --- |
| Force Updated Clients | 0 | Cannot fall back to insecure versions | Rejects unpatched clients |
| Mitigated | 1 | Cannot fall back to insecure versions | Accepts unpatched clients |
| Vulnerable | 2 | Can fall back to insecure versions | Accepts unpatched clients |

Three pairs are blocked: an unpatched client with a Force Updated Clients server, a Force Updated Clients client with an unpatched server, and a Mitigated client with an unpatched server. Do not deploy Force Updated Clients until every remote host is updated.

The fix is to update and restart both machines. Supported Windows 11 and Server 2025 builds already have the update, so the other end is usually an old host or one waiting for a reboot. Check the value:

```
reg query "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters" /v AllowEncryptionOracle
```

To reach an unpatched server before it is updated, set Vulnerable on the affected client only (restart required). Microsoft calls this a workaround to use temporarily, if at all. Patch the server, then set the client back to Mitigated.

```
reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters" /v AllowEncryptionOracle /t REG_DWORD /d 2 /f
```

Microsoft’s other temporary workaround, setting the security layer to RDP and disabling NLA on the server, weakens the connection further. Treat it as a last resort.

## User rights and the Remote Desktop Users group

These are the GPO fields that most often break RDP sign-in. All of them live under:

```
Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment
```

- **Allow log on through Remote Desktop Services.** By default this is Administrators and Remote Desktop Users on workstations and member servers, and Administrators only on domain controllers. A GPO that lists only Administrators locks everyone else out.

- **Deny log on through Remote Desktop Services.** This supersedes the Allow right.

- **Access this computer from the network.** NLA authentication is a network logon. If a GPO removed Everyone and did not add Remote Desktop Users, NLA fails with “restricted the types of logon”.

- **Deny access to this computer from the network.** The user must not be in it, directly or through a group, or NLA fails.

Membership of Remote Desktop Users is the normal way to grant access. On a standalone machine:

```
Add-LocalGroupMember -Group "Remote Desktop Users" -Member "CORP\jsmith"
```

Group Policy overrides local security policy, so check what applies on the target:

```
gpresult /h C:\Temp\rsop.html
gpupdate /force
```

If the expected GPO is missing, see [Group Policy not applying](/guides/group-policy-not-applying/).

## Security layer and TLS settings

Require use of specific security layer for remote (RDP) connections, in the same Security folder, has three options:

- **Negotiate:** uses the most secure method the client supports. TLS is used if available; otherwise native RDP encryption, and the server is not authenticated.

- **RDP:** native RDP encryption only. The server is not authenticated.

- **SSL (TLS):** TLS is required to authenticate the server. If TLS is not supported, the connection fails. Microsoft lists this as the recommended setting.

If connections fail after choosing SSL, check the server’s RDP certificate. Set client connection encryption level applies only to native RDP encryption, not TLS.

## Restricted Admin and Remote Credential Guard

These stop reusable credentials reaching the remote host. Two policies under Administrative Templates, System, Credentials Delegation control them:

- On the target: Remote host allows delegation of non-exportable credentials must be enabled.

- On the client: Restrict delegation of credentials to remote servers, with a mode such as Require Remote Credential Guard or Restrict Credential Delegation.

To use it for one connection, run `mstsc.exe /remoteGuard`. Remote Credential Guard needs Kerberos and does not allow NTLM fallback. It only works for direct connections, not through RD Gateway or RD Connection Broker, and the target must be joined to Active Directory, not Microsoft Entra ID. Windows does not try Kerberos when you connect by IP address, so use the host name. If you have restricted NTLM, see [disable NTLM in Active Directory](/guides/disable-ntlm-active-directory/). “Account restriction is preventing this user from signing in” usually points to one of these restrictions.

## Locked, disabled or expired accounts with NLA

NLA checks credentials before the session starts, so the user never reaches a sign-in screen. Locked or disabled accounts fail, and a user with an expired or must-change password cannot change it there. Unlock or reset the account, or let the user change it from another machine; in an RDS deployment, RD Web Access can offer password change. The Security log shows the reason:

| Status in event 4625 | Meaning |
| --- | --- |
| 0xC000006A | Bad password |
| 0xC0000064 | User name does not exist |
| 0xC0000234 | Account locked out |
| 0xC0000072 | Account disabled |
| 0xC0000071 | Password expired |
| 0xC0000224 | Password must be changed before first logon |
| 0xC000015B | User has not been granted the requested logon type |

For reading these events in bulk, see [Event ID 4625 failed logon](/guides/event-id-4625-failed-logon/).

## Time skew and Kerberos

Kerberos fails when clocks differ by more than Maximum tolerance for computer clock synchronization (5 minutes by default). RDP then shows the “time or date difference” error. Compare clocks and resynchronise the wrong one:

```
net time \\
net stop w32time
net start w32time
w32tm /resync
```

If the clocks agree, check DNS. If a restart clears it for days at a time, Microsoft points to TCP port exhaustion. A local account can still sign in meanwhile.

## Check the event logs

A CredSSP block is logged on the patched client as event 6041 (LSA, LsaSrv) in the System log: “failed to negotiate a common protocol version”. On the target, event 1149 in the RemoteConnectionManager log records successful user authentication.

```
# On the client
Get-WinEvent -FilterHashtable @{LogName='System'; Id=6041} -MaxEvents 10

# On the target
Get-WinEvent -FilterHashtable @{LogName='Microsoft-Windows-TerminalServices-RemoteConnectionManager/Operational'; Id=1149} -MaxEvents 10
Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4625} -MaxEvents 20
```

With NLA, the credential check is a network logon, so the first 4624 or 4625 for the attempt usually shows Logon Type 3. The session itself is Logon Type 10, so searching only for type 10 misses NLA failures. More in [RDP connection logs and event IDs](/guides/rdp-connection-logs-event-ids/).

## Troubleshooting table

| Symptom | Cause | Fix |
| --- | --- | --- |
| “This could be due to CredSSP encryption oracle remediation” | One end unpatched or not restarted | Update and restart both ends; Vulnerable on the client only, briefly |
| “The system administrator has restricted the types of logon” | Missing Access this computer from the network or Allow log on through Remote Desktop Services, or a Deny right applies | Fix the user rights in the GPO, confirm with gpresult /h |
| “The user account is not authorized for remote login” | Not in Remote Desktop Users and not otherwise granted the Allow right | Add the user or group to Remote Desktop Users |
| “Time or date difference” error | Clock skew beyond the Kerberos tolerance | Resync time with w32tm /resync; check DNS if it persists |
| “Account restriction is preventing this user from signing in” | Remote Credential Guard or a similar restriction | Connect directly by host name, or turn the restriction off for that path |
| Works by host name but not by IP address | No Kerberos for IP addresses, and NTLM is blocked or not allowed | Connect by host name or FQDN |
| User with an expired password cannot connect | NLA authenticates before any password change prompt | Reset the password, or change it from another machine |
| No option to enable Remote Desktop on a Surface or laptop | Windows Home edition cannot host RDP | Upgrade to Pro, or use another remote access tool |

How this was checked: settings, paths, registry values and event IDs verified against Microsoft’s documentation (November 2026); not run in our lab.

**Official documentation:** [CredSSP updates for CVE-2018-0886](https://support.microsoft.com/en-us/help/4093492), [User can’t authenticate or must authenticate twice](https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/cannot-authenticate-must-authenticate-twice), [The system administrator has restricted the types of logon](https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/system-admin-restrict-types-logon), [Remote Desktop cannot verify the identity of the remote computer](https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/remote-desktop-cannot-verify-identity-connecting-remote-machine), [Remote Credential Guard](https://learn.microsoft.com/en-us/windows/security/identity-protection/remote-credential-guard).

**Related guides:** [Enable Remote Desktop with Group Policy](/guides/enable-remote-desktop-group-policy/) · [RDP connection logs and event IDs](/guides/rdp-connection-logs-event-ids/) · [Event ID 4625 failed logon](/guides/event-id-4625-failed-logon/) · [Group Policy not applying](/guides/group-policy-not-applying/) · [Disable NTLM in Active Directory](/guides/disable-ntlm-active-directory/).

## Frequently asked questions

### How do I enable RDP with Network Level Authentication in Windows 11?

Open Settings, System, Remote Desktop and turn Remote Desktop on. For many machines, enable the Group Policy setting Require user authentication for remote connections by using Network Level Authentication. The PC must run Pro, Enterprise or Education.

### Is it safe to set Encryption Oracle Remediation to Vulnerable?

Only briefly. Vulnerable lets the client fall back to insecure CredSSP versions. Patch and restart the server, then set the client back to Mitigated.

### Which Group Policy settings can cause Remote Desktop authentication to fail?

The common ones are Allow log on through Remote Desktop Services, Deny log on through Remote Desktop Services, Access this computer from the network, Deny access to this computer from the network, Encryption Oracle Remediation, Require use of specific security layer for remote (RDP) connections and Restrict delegation of credentials to remote servers.

### Can I enable Remote Desktop on a Surface Go?

Only if it runs Windows Pro or higher. Windows Home cannot accept incoming connections. Check the edition in Settings, System, About.

### Why can’t a user with an expired password connect over RDP?

NLA checks credentials before a session starts, so the user never reaches the password change screen. Reset the password or change it from another machine.
