Fix Remote Desktop (RDP) Not Working on Windows 10/11: Enable, Firewall, and Port Checks
Difficulty: Intermediate |
Time Required: 20 minutes
Remote Desktop Protocol (RDP) is one of the fastest ways to access a Windows PC remotely—but when it stops working, you’re left with vague errors like
“Remote Desktop can’t connect to the remote computer” or a connection that times out. This guide walks you through the most common causes on Windows 10/11:
RDP not enabled,
blocked by firewall,
wrong network profile, or
port 3389 not reachable. By the end, you’ll have a reliable checklist to get RDP connecting again.
Prerequisites
Before you start, confirm these basics:
- You have administrator access to the remote PC (the one you’re trying to connect to).
- The remote PC is powered on and not sleeping/hibernating.
- You know the remote PC’s IP address or hostname.
- You’re using a Windows edition that supports hosting RDP:
- Windows 10/11 Pro, Enterprise, Education can accept inbound RDP.
- Windows 10/11 Home cannot host inbound RDP (you can still use Remote Desktop client).
Note (Windows editions): If the remote PC is Windows Home, you’ll need alternatives like Quick Assist, third-party remote tools, or upgrading to Pro.
Step-by-step: Fix RDP not working
1) Confirm the remote PC supports inbound Remote Desktop
- On the remote PC, go to Settings → System → About.
- Under Windows specifications, check Edition.
If it says
Home, inbound RDP hosting isn’t supported.
2) Enable Remote Desktop on the remote PC (Windows 10/11)
- On the remote PC, open Settings.
- Go to:
- Windows 11: Settings → System → Remote Desktop
- Windows 10: Settings → System → Remote Desktop
- Turn Remote Desktop to On.
- When prompted, click Confirm.
Optional but recommended:
- Click Remote Desktop users (or Select users that can remotely access this PC) and ensure your account (or a group) is allowed.
Warning: Only enable RDP on networks you trust, and avoid exposing RDP directly to the internet unless you know how to secure it properly (VPN + strong auth).
3) Verify the Remote Desktop service is running
Sometimes the setting is enabled but the service is stopped.
- Press Win + R, type
services.msc, press Enter.
- Find Remote Desktop Services.
- Ensure:
- Status: Running
- Startup Type: Manual or Automatic (Manual is normal; it starts when needed)
- If it’s not running, right-click → Start.
Also check:
- Remote Desktop Services UserMode Port Redirector (helps with device redirection; not always required for basic RDP, but good to be running).
4) Make sure Network Level Authentication (NLA) isn’t blocking you
NLA is more secure, but older clients or misconfigured accounts can fail.
- Press Win + R, type
sysdm.cpl, press Enter.
- Go to the Remote tab.
- Under Remote Desktop, verify the option:
- Allow remote connections to this computer is selected.
- If you’re troubleshooting, temporarily uncheck:
- Allow connections only from computers running Remote Desktop with Network Level Authentication
Tip: If disabling NLA fixes it, the real issue may be credentials, domain trust, time sync, or an outdated RDP client. Re-enable NLA once resolved.
5) Check Windows Firewall rules for Remote Desktop
The most common RDP failure is a blocked inbound rule.
- On the remote PC, open Windows Security.
- Go to Firewall & network protection.
- Click Allow an app through firewall.
- Click Change settings.
- Ensure Remote Desktop is allowed on the correct network types:
- Private (typical home/office LAN)
- Public (usually not recommended)
Better method (more reliable):
- Press Win + R, type
wf.msc, press Enter.
- Click Inbound Rules.
- Locate rules named Remote Desktop - User Mode (TCP-In) and (UDP-In).
- Ensure they are:
- Enabled
- Action: Allow
- Profile: Matches your network (Private/Domain)
Note: RDP uses TCP 3389 by default. UDP is optional but improves performance. Start with TCP.
6) Confirm the remote PC’s network profile is correct (Public vs Private)
If the remote PC is marked as
Public, firewall rules may be more restrictive.
- On the remote PC, go to Settings → Network & internet.
- Click your active connection (Wi‑Fi or Ethernet).
- Set Network profile to Private (if it’s a trusted network).
Warning: Don’t set a network to Private on untrusted public Wi‑Fi.
7) Verify the remote PC’s IP address and name resolution
If you’re trying to connect to the wrong address, RDP will fail regardless of settings.
On the remote PC:
- Open Command Prompt.
- Run:
ipconfig
- Note the IPv4 Address.
From the client PC (the one you’re connecting from):
- Try ping (may be blocked, but it’s a quick test):
ping <remote-ip>
- If using a hostname, try:
nslookup <remote-hostname>
Tip: If hostname fails but IP works, you have a DNS/NetBIOS/name resolution issue. Use the IP or fix local DNS.
8) Check if port 3389 is listening on the remote PC
On the remote PC, open
PowerShell as Admin and run:
netstat -an | findstr ":3389"
You want to see something like
LISTENING on
0.0.0.0:3389 or
:::3389.
If nothing is listening:
- Remote Desktop may not be enabled correctly,
- the service may not be running,
- or RDP may be configured to a different port.
9) Test port connectivity from the client PC (best firewall/port check)
On the client PC, open
PowerShell and run:
Test-NetConnection <remote-ip> -Port 3389
- If TcpTestSucceeded : True, the port is reachable.
- If False, something is blocking it (firewall, router, VPN rules, or incorrect IP).
Note: If you’re on different networks (outside the home/office), port forwarding/NAT or a VPN may be required. For security, prefer VPN over exposing RDP to the internet.
10) If the RDP port was changed, confirm (or reset) the port
Some systems change RDP to a non-default port. To check:
- On the remote PC, open Registry Editor (
regedit).
- Go to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
- Find PortNumber (DWORD).
- It’s displayed in decimal if you switch the view (right-click → Modify).
If you change it, you must also:
- update the firewall inbound rule to match the new port,
- connect using
IP:PORT (example: 192.168.1.50:3390).
Warning: Editing the registry incorrectly can break Windows. Consider making a restore point first.
Tips and troubleshooting notes
- Account/permissions issue: The account must have a password (blank passwords often fail) and be allowed in Remote Desktop Users or be an admin.
- Credential errors: Try
.\username for local accounts, or COMPUTERNAME\username.
- Sleep/hibernation: If the remote PC sleeps, RDP won’t connect. Check Power & battery → Screen and sleep.
- Multiple firewalls/security suites: Third-party security software can override Windows Firewall rules.
- VPNs and “Public network”: Some VPNs set the profile to Public and block inbound connections.
- Router/firewall upstream: Even if Windows allows it, a router ACL or corporate firewall may block TCP 3389.
- Safer remote access recommendation: If you need remote access over the internet, use a VPN (WireGuard, OpenVPN, Windows built-in VPN) and keep RDP limited to LAN/VPN only.
Conclusion
When Remote Desktop stops working, the fix is usually straightforward once you check the essentials in the right order:
RDP enabled,
service running,
firewall rules correct, and
port 3389 reachable. Using
Test-NetConnection and verifying listening ports quickly tells you whether the issue is local configuration or network blocking.
Key Takeaways:
- Enable Remote Desktop and confirm the Remote Desktop Services service is running.
- Ensure Windows Firewall inbound rules for Remote Desktop are enabled for the correct network profile.
- Use
Test-NetConnection -Port 3389 to confirm whether the problem is connectivity/port blocking vs. credentials/settings.
- If connecting across networks, prefer VPN instead of exposing RDP directly to the internet.
This tutorial was generated to help WindowsForum.com users get the most out of their Windows experience.