Search guides

Fix a remote desktop that will not connect

We'll confirm the host PC is on and reachable, check port 3389 and firewall, verify credentials and network—or tell you when to contact IT.

Troubleshooting · Wi‑Fi & networking
10–25 min
What you'll need
  • Access to the host PC (to enable RDP and check firewall)
  • Access to the client device
  • Network access (same network or VPN)
Step 1 of 5

Quick triage — pick your path

Quick triage — pick your path

Choose the option that matches what you see. You can jump straight to that section.

Show full guide

Steps

Goal: Confirm the host PC is on and reachable, then isolate the cause—RDP, port 3389, credentials, or firewall.

Check host first

Goal: Rule out host or network problems before troubleshooting RDP.

  • Check the host PC is on and connected. Ping the host IP from the client. If the host does not reply, fix the host or network first.
  • Good: Host replies. Proceed to RDP and port 3389.
  • Bad: No reply—check the host is on and the network is working. See Fix device that loses connection.

RDP and port 3389

Goal: Check that RDP is enabled and port 3389 is open.

  • On the host PC, open Settings > System > Remote Desktop and turn on Remote Desktop. In the firewall, allow inbound connections on port 3389. If you connect from outside the network, set up port forwarding on the router.
  • Good: RDP is enabled and port 3389 is open. Proceed to Credentials and firewall.
  • Bad: RDP is off or port is blocked—fix those first.

Credentials and firewall

Goal: Verify credentials and rule out firewall blocking.

  • Use the correct username and password. The username may need the host name (e.g. HOSTNAME\username). Add an exception for RDP in the firewall on the host and client. If the network requires a VPN, connect to the VPN first.
  • Good: RDP connects.
  • Bad: Still fails—contact IT with the error message and network context.

When to get help

Contact IT if:

  • RDP still will not connect after checking the host, port 3389, credentials, and firewall.
  • You get a specific error (e.g. authentication failed, connection timed out).
  • You are on a work or school network and RDP may be restricted—check with IT.

Verification

  • The RDP client connects and shows the host desktop.
  • You can log in with your credentials.
  • No error messages or timeout when connecting.

Escalation ladder

Work from the device outward. Stop when the problem is fixed.

  1. Confirm host Check host PC is on and pingable.
  2. RDP and port 3389 Enable RDP on host; allow port 3389 in firewall.
  3. Credentials Verify username and password (include host name if needed).
  4. Firewall and VPN Add firewall exception; connect to VPN if required.
  5. Contact IT Provide error message and network context.

What to capture if you need help

Before calling support or posting for help, have these ready. It speeds everything up.

  • Host PC name and IP
  • Error message shown
  • Whether connecting from same network or remote
  • Steps already tried

Is the host PC on and reachable?

Ping the host IP from the client. If no reply, the host is off or unreachable.

Check the host PC is powered on and connected to the network. Ping the host IP from the client. Good: host replies—proceed to RDP check. Bad: no reply—fix the host or network first (see fix-device-loses-connection).

Yes No

You can change your answer later.

Fix host or network first

Fix the host or network first. When the host is reachable, return to this guide.

Done

Is Remote Desktop enabled and port 3389 open?

RDP must be enabled on the host. Port 3389 must be allowed in the firewall.

On the host, enable Remote Desktop in Settings. Allow port 3389 in the firewall. Good: RDP enabled and port open—proceed to credentials. Bad: RDP off or port blocked—fix those first.

Yes No

You can change your answer later.

Are credentials correct and is VPN required?

Wrong credentials or missing VPN can block the connection.

Verify username and password. Use HOSTNAME\\username if needed. If the network requires VPN, connect to VPN first. Good: credentials correct and VPN connected if required—RDP should connect. Bad: wrong credentials or VPN not connected—fix those.
Question

Are credentials correct and VPN connected if required?

Continue

You can change your answer later.

Contact IT

Contact IT with the error message and whether you are on the same network or remote. Confirm you have tried all steps.

Done

Reviewed by Blackbox Atlas

Rate this guide

Was this helpful?

Continue to