10 Common RDP Connection Problems and How to Fix Them

Few things are more frustrating than RDP connection problems: you need to reach a remote computer and are greeted by a vague error message instead. The good news is that most Remote Desktop Protocol (RDP) connection failures come from a short list of familiar causes — a wrong computer name, a blocked port, an authentication mismatch, or a service that simply is not running. This RDP connection problems fix guide covers the ten most common causes with concrete, step-by-step fixes for each. Work through them in order, and you will resolve the overwhelming majority of connection failures.

1. “Remote Desktop can’t find the computer” — Wrong

Name or IP Address

Why it happens: The client cannot resolve the computer name you typed, or the IP address has changed (very common on home networks where routers assign addresses dynamically). If you are new to the client itself, see our guide to using Remote Desktop Connection on Windows.

How to fix it:

1. On the host PC, press Win + R, type cmd, and run ipconfig. Note the IPv4 Address.
2. In the Remote Desktop client, try connecting with the IP address instead of the PC name.
3. If the IP works but the name does not, your network’s name resolution is the issue — keep using the IP, or set a DHCP reservation in your router so the address never changes.
4. Double-check for typos: even one wrong character in the computer name will fail.

2. Remote Desktop Is Not Enabled on the Host

Why it happens: The feature was never turned on, was disabled by an update or policy, or the PC runs Windows Home (which cannot host sessions). See our guide to enabling Remote Desktop on Windows 10/11 for the full walkthrough.

How to fix it:

1. On the host PC, open Settings > System > Remote Desktop and confirm the toggle is On.
2. Alternatively, press Win + R, type sysdm.cpl, go to the Remote tab, and select Allow remote connections to this computer.
3. Verify the Windows edition under Settings > System > About — it must be Pro, Enterprise, or Education to host.

3. Network Level Authentication (NLA) Credential Errors

Why it happens: NLA requires your credentials to be verified before the session starts. Errors here usually mean a wrong username format, a mistyped password, or an account without a password.

How to fix it:

1. Use the full username format: .\username for a local account (the dot means “this computer”), or username@computername.
2. Confirm the account actually has a password — RDP rejects blank passwords.
3. Make sure the account is in the Remote Desktop Users group: open sysdm.cpl > Remote tab > Select Users and add it if missing.
4. If the password was recently changed, sign in locally once on the host first to clear any cached credential state.

4. Windows Firewall Is Blocking the Connection

Why it happens: The Remote Desktop firewall exception is disabled, or a third-party firewall/antivirus is blocking inbound TCP port 3389.

How to fix it:

1. On the host, go to Control Panel > System and Security > Windows Defender Firewall > Allow an app or feature.
2. Ensure Remote Desktop is checked for the network type you are on (Private, at minimum).
3. For a precise check, run wf.msc and confirm the Inbound Rule named Remote Desktop – User Mode (TCP-In) is enabled.
4. If you use third-party security software, add an exception for TCP port 3389 there as well.
5. As a quick diagnostic only, you can temporarily disable the firewall to test — but re-enable it immediately afterward and create the proper rule instead of leaving it off.

5. The Remote Desktop Services Service Is Not Running

Why it happens: The background service that listens for RDP connections (TermService) has stopped or is set to manual startup.

How to fix it:

1. Press Win + R, type services.msc, and press Enter.
2. Find Remote Desktop Services in the list.
3. If its status is blank or Stopped, right-click it and choose Start.
4. Right-click again, choose Properties, and set Startup type to Automatic so it survives reboots.
5. Verify the PC is listening: in an elevated Command Prompt, run netstat -ano | findstr 3389 — you should see a LISTENING entry.

6. Port Forwarding or NAT Issues for Internet Connections

Why it happens: When connecting over the internet, your router must forward TCP port 3389 to the host PC. If the rule points to an old IP address, or the ISP uses carrier-grade NAT, the connection never arrives.

How to fix it:

1. Confirm the host PC’s current local IP with ipconfig and compare it to the router’s port-forwarding rule — update the rule if they differ.
2. Better yet, create a DHCP reservation for the host PC in the router so its IP never changes.
3. From outside the network, test with Test-NetConnection -ComputerName <public-IP> -Port 3389 in PowerShell; TcpTestSucceeded: True means the port is reachable.
4. If your ISP uses CGNAT (common with some mobile and fiber providers), inbound port forwarding may be impossible — in that case, use a VPN into your network instead.

7. CredSSP “Encryption Oracle” Error After Windows Updates

Why it happens: You may see “An authentication error has occurred. The function requested is not supported… This could be due to CredSSP encryption oracle remediation.” This appears when the client is patched but the host is not (or vice versa), after the 2018 CredSSP security updates.

How to fix it:

1. The correct fix: install all pending Windows Updates on both the client and the host, then reboot both. This resolves the mismatch permanently.
2. Only as a temporary workaround (it lowers security), an administrator can set the Group Policy Computer Configuration > Administrative Templates > System > Credentials Delegation > Encryption Oracle Remediation to Enabled with protection level Vulnerable — then update both machines as soon as possible and revert the setting.

8. “The Logon Attempt Failed” — Account or Password Problems

Why it happens: Wrong password, a locked or disabled account, or an account that lacks remote logon rights.

How to fix it:

1. Verify the password by signing in locally on the host PC.
2. Check the account is not locked out: open lusrmgr.msc > Users, right-click the account, and clear Account is locked out if present.
3. Confirm the account has not expired or been disabled in the same tool.
4. If the PC is domain-joined, make sure you are using domain credentials in the format DOMAIN\username, not a local account name.

9. Black Screen, Freezing, or Dropped Sessions

Why it happens: Display driver issues, insufficient resources on the host, or an unstable network connection.

How to fix it:

1. In the RDP client, click Show Options > Display and lower the color depth, or under Experience choose a slower connection speed to reduce bandwidth.
2. Disable Persistent bitmap caching under the Experience tab — this resolves many black-screen cases.
3. On the host, update the graphics driver and install Windows Updates.
4. Press Ctrl + Alt + End inside the session and choose Sign out, then reconnect fresh — this clears corrupted session state.
5. If disconnections happen on Wi-Fi, test with a wired connection to rule out wireless instability.

10. “An Internal Error Has Occurred”

Why it happens: This generic message can stem from corrupted RDP configuration, mismatched security layer settings, or a problematic Windows update.

How to fix it:

1. On the client, open the Remote Desktop client options, go to the Advanced tab, and under Connect from anywhere click Settings to verify no stale gateway configuration exists.
2. Delete any saved .rdp files for this connection and recreate the connection from scratch (stale saved settings are a frequent culprit).
3. On the host, check Event Viewer (eventvwr.msc > Windows Logs > System) around the time of the failure for TerminalServices errors that point to the real cause.
4. Ensure both machines are fully updated — several Windows updates have specifically fixed RDP internal errors.

RDP Connection Problems Fix: Quick Checklist

When you are in a hurry, run through this five-minute checklist before diving into the detailed fixes above:

• Is the host PC powered on and awake (not in sleep mode)?
• Are you using the correct computer name or IP address?
• Is Remote Desktop enabled on the host, on a Pro-or-higher edition?
• Is the Windows Firewall rule for Remote Desktop enabled?
• Does your account have a password and permission to connect?

Conclusion

Almost every RDP connection failure traces back to one of these ten causes. The pattern to remember is simple: verify the host is enabled and reachable, confirm the network path (firewall, port, NAT), then check authentication (credentials, NLA, account state). Keeping both machines updated prevents an entire category of these errors from ever appearing. Bookmark this guide — the next time a connection fails, you will know exactly where to look. For edge cases beyond these ten, Microsoft’s official Remote Desktop troubleshooting documentation is the authoritative next step.

Frequently Asked Questions

Why does Remote Desktop say my credentials are wrong when they are correct?

This is usually a username format issue rather than a wrong password. Try .\username for local accounts, confirm the account has a password set, and make sure it belongs to the Remote Desktop Users group on the host.

Can a Windows update break Remote Desktop connections?

Yes. The best-known example is the CredSSP encryption oracle update, which blocks connections between patched and unpatched machines. The fix is always to update both sides. Keeping automatic updates enabled on both machines prevents most of these mismatches.

How do I know if port 3389 is reachable from outside my network?

From a computer outside your network, run Test-NetConnection -ComputerName <your-public-IP> -Port 3389 in PowerShell. If TcpTestSucceeded returns True, the port is open and forwarded correctly.

Should I disable the firewall to fix RDP problems?

Only as a momentary diagnostic test — never as a permanent solution. If disabling the firewall fixes the connection, you have confirmed the cause; re-enable the firewall immediately and create a proper inbound rule for Remote Desktop instead.