All articles
TutorialsJan 26, 2026 · 11 min read

Remote Desktop Can't Connect — How to Fix It

Remote Desktop Can't Connect — How to Fix It

You try to connect and get the dreaded "Remote Desktop can't connect to the remote computer" error. Or maybe it just times out. Or it connects but immediately disconnects.

These errors have a handful of common causes. Here's how to track down the problem and fix it.

Most Common Error Messages

"Remote Desktop can't connect to the remote computer for one of these reasons..." This generic error usually means the server isn't reachable — wrong IP, firewall blocking, or server is down.

"Your credentials did not work" Wrong username or password. Sometimes it's a domain issue.

"The connection was denied because the user account is not authorized for remote login" The account exists but doesn't have RDP permission.

"Remote Desktop can't verify the identity of the remote computer" Certificate issue. Usually safe to bypass.

"The connection timed out" Can't reach the server at all.

Let's fix each one.

Fix 1: Verify the IP Address and Port

The most common issue. Double-check you have the right IP.

Also check the port. RDP uses port 3389 by default, but many providers use custom ports for security (like 33890 or 12345).

How to specify a custom port: Instead of just 185.193.125.42, use 185.193.125.42:12345

Quick test: Open PowerShell or Command Prompt and run:

telnet 185.193.125.42 3389

If you get a blank screen or connection, the port is open. If it says "connection refused" or times out, the port is blocked or wrong.

No telnet? Use this instead:

Test-NetConnection -ComputerName 185.193.125.42 -Port 3389

Fix 2: Check if RDP is Enabled on the Server

If you have console access (through your hosting provider's panel), verify RDP is turned on:

  1. Right-click "This PC" → Properties
  2. Click "Remote settings" on the left
  3. Under Remote Desktop, select "Allow remote connections to this computer"
  4. Uncheck "Allow connections only from computers running Remote Desktop with NLA" (if you're having auth issues)

Fix 3: Windows Firewall Rules

The Windows Firewall might be blocking RDP. Check these rules are enabled:

  1. Open Windows Firewall with Advanced Security
  2. Click "Inbound Rules"
  3. Find "Remote Desktop - User Mode (TCP-In)"
  4. Make sure it's enabled (green checkmark)

Also check for any third-party firewalls or security software that might block port 3389.

If you changed the RDP port, you need a custom firewall rule:

netsh advfirewall firewall add rule name="RDP Custom Port" dir=in action=allow protocol=tcp localport=YOUR_PORT

Fix 4: Credentials Not Working

"Your credentials did not work" can mean several things:

Wrong password: The obvious one. Make sure Caps Lock is off and try typing the password in Notepad first to verify.

Wrong username format: Try these variations:

  • Administrator
  • .\Administrator (local account)
  • SERVERNAME\Administrator
  • [email protected] (if domain-joined)

Account locked: After too many failed attempts, Windows locks the account. If you have console access, check Local Users and Groups.

NLA authentication issue: If you're connecting from an older client, Network Level Authentication might fail. Disable NLA on the server (Remote Desktop settings → uncheck the NLA requirement).

Fix 5: User Not Authorized for Remote Login

The account might not be in the "Remote Desktop Users" group.

Add user to Remote Desktop Users:

  1. Open Computer Management
  2. Go to Local Users and Groups → Groups
  3. Double-click "Remote Desktop Users"
  4. Add the user account

Note: Administrator accounts can always connect via RDP regardless of group membership.

Fix 6: Certificate Errors

If you get a certificate warning, you can usually just click "Yes" to proceed. This happens because:

  • The server uses a self-signed certificate
  • The certificate doesn't match the IP/hostname

This isn't a security risk if you trust the server. To suppress the warning permanently, you'd need to install a proper certificate, which most people don't bother with for personal servers.

If you're scripting connections and need to bypass the warning:

mstsc /v:server-ip /admin

Or in your RDP file, add:

authentication level:i:0

Fix 7: Network Issues

If nothing above works, the problem might be between you and the server.

Test basic connectivity:

ping 185.193.125.42

If ping fails, either:

  • The server is down
  • Your ISP is blocking traffic
  • There's a routing issue

Trace the route:

tracert 185.193.125.42

Look for where the packets stop or get high latency. This helps identify if the problem is your network, your ISP, or the hosting provider.

Try from a different network: If possible, test from your phone's mobile data (hotspot) or a VPN. If it works from there, your regular network has an issue.

Fix 8: Server-Side Issues

Sometimes the server itself is the problem.

Remote Desktop Services not running: The RDP service might have stopped or crashed.

If you have console access:

  1. Open Services (services.msc)
  2. Find "Remote Desktop Services"
  3. Make sure it's running; restart it if needed

Server out of resources: If the server has no RAM or disk space left, new RDP sessions fail. Check Task Manager through console access.

Too many users: Windows limits concurrent RDP sessions (2 for workstation editions, more for Server with RDS licenses). If you're the third person trying to connect to a standard server, you'll be denied.

Fix 9: Local Windows Settings

Your own Windows machine might be the issue.

Network type: If your network is set to "Public", some RDP features are restricted.

  1. Open Settings → Network & Internet
  2. Click on your connection
  3. Set network profile to "Private"

RDP client corrupted: Try resetting the Remote Desktop client:

  1. Delete %LOCALAPPDATA%\Microsoft\Terminal Server Client\Cache
  2. Delete any saved .rdp files and recreate them

Group Policy blocking RDP: In corporate environments, IT might have disabled outbound RDP. Check with your IT department.

Quick Troubleshooting Checklist

Work through this list:

Check How
Correct IP address? Verify with provider
Correct port? Test with telnet or Test-NetConnection
Server online? Check provider's status page or console
RDP enabled on server? Check Remote Desktop settings
Firewall allowing 3389? Check Windows Firewall rules
Correct username format? Try .\Administrator
Password correct? Test by typing in Notepad first
Account locked? Check Local Users after console access
User in RDP group? Check Remote Desktop Users group
Server has resources? Check RAM/CPU via console
Different network works? Try phone hotspot

Still Can't Connect?

If you've checked everything:

  1. Contact your hosting provider. They can check the server from their end and see if there are network issues.

  2. Check the provider's status page. There might be maintenance or an outage.

  3. Request console access. Most providers offer VNC or IPMI access that works even when RDP doesn't.

  4. Consider a server reboot. Sometimes Windows just needs a restart. Your provider's panel should have a reboot option.

Most RDP connection issues come down to firewalls, wrong credentials, or the server being unreachable. Systematic troubleshooting usually finds the cause within a few minutes.