Fix Remote Desktop Can’t Connect: 7 Reasons

If Remote Desktop says it can’t connect to the remote computer, the cause is almost always one of three things: the remote PC is unreachable on the network, the Remote Desktop service isn’t running, or credentials/encryption settings don’t match. This guide walks through the most common reasons for the error and the exact steps to fix each one, from enabling Remote Desktop in Windows settings to adjusting firewall rules and checking your local network.

Why Remote Desktop Connection Fails

Remote Desktop Protocol (RDP) is a client-server protocol built into Windows. When you try to connect, your client sends a request to port 3389 on the target machine. The target must be powered on, awake, connected to the network, have Remote Desktop enabled, and be running the Remote Desktop Services service. Any break in that chain produces an error. The full error message usually reads: “Remote Desktop can’t connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned off 3) The remote computer is not available on the network.” That message is deliberately generic—Windows doesn’t tell you which of the three it is, so you have to check each one.

Check if Remote Desktop Is Enabled

The most common fix is simply turning on Remote Desktop on the target PC. On Windows 10 and 11, go to Settings > System > Remote Desktop and toggle it on. On Windows Pro or Enterprise, you’ll also see a checkbox for Network Level Authentication (NLA). Leave it enabled unless you’re connecting from a very old client. If the toggle is grayed out, your edition of Windows may not support Remote Desktop—Home editions only allow incoming connections with third-party tools, not the built-in RDP host. To verify, open System Information and look at the “OS Name” line; if it says “Home,” you’ll need an alternative like Chrome Remote Desktop or a VNC client.

Verify the Target PC Is On and Reachable

If Remote Desktop is enabled, the next step is to confirm the computer is actually on and online. Wake-on-LAN can make a sleeping PC appear off, so check the power settings on the target: go to Control Panel > Power Options > Change plan settings > Change advanced power settings and set “Sleep” to Never, or at least disable “Allow hybrid sleep.” Then, from the client machine, open Command Prompt and run ping <IP address>. If you get replies, the host is reachable. If you get “Request timed out,” the host may be off, on a different subnet, or blocked by a firewall. Also try pinging the computer name—if it resolves, DNS is working; if not, you may need to use the IP address directly.

Fix Firewall and Network Profile Issues

Windows Defender Firewall normally allows RDP traffic automatically when you enable Remote Desktop, but a third-party firewall or a changed network profile can block it. On the target PC, open Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall and look for “Remote Desktop.” Make sure both Private and Public checkboxes are ticked. If it’s missing, click “Change settings” then “Allow another app” and browse to C:\Windows\System32\mstsc.exe. Also check the network profile: if the target is on a “Public” network, some firewall rules are stricter. Change it to “Private” in Settings > Network & Internet > Wi-Fi/ Ethernet > Properties if you trust the network. For a custom firewall, you’ll need to open TCP port 3389 inbound.

Restart the Remote Desktop Services

Sometimes the Remote Desktop Services service stops or hangs. On the target PC, press Win + R, type services.msc, and press Enter. Find Remote Desktop Services (TermService) and Remote Desktop Configuration (SessionEnv). Both should be running. If they’re not, right-click and select Start. If they are running but connections still fail, restart them: right-click > Restart. Also check Remote Desktop Services UserMode Port Redirector (UmRdpService) and start it if needed. After restarting, try connecting again. If the service fails to start, look in Event Viewer under Windows Logs > System for error codes—common ones include 7024 (service terminated) or 7031 (crashed).

Check Credentials and NLA Settings

Even with everything else correct, wrong credentials produce the same generic error. Make sure you’re using the username in the format COMPUTERNAME\Username or IP\Username for local accounts, or DOMAIN\Username for domain accounts. If you’re connecting from a different Windows version, Network Level Authentication can cause a failure. On the client, open the Remote Desktop app, click “Show Options,” go to the Advanced tab, and ensure “Require NLA” is checked only if the host supports it. If you’re unsure, uncheck it—it’s less secure but works with older hosts. Also verify the password is correct; a typo here gives the same “can’t connect” message.

Verify IP Address and Port Forwarding (for Remote Access)

If you’re connecting from outside your local network, you need the public IP of the router and port forwarding set up. On the target PC, find its local IP with ipconfig (e.g., 192.168.1.100). Then log into your router’s admin page and forward TCP port 3389 to that IP. Be aware that exposing RDP directly to the internet is a security risk—hackers constantly scan for open port 3389. A safer approach is to use a VPN or a Remote Desktop Gateway. Also note that your public IP may change; use a dynamic DNS service if you need a stable hostname. If you’re on a corporate network, the IT department may block outbound RDP, so you’ll need to ask them to open it.

Advanced Troubleshooting: Group Policy and Registry

In some cases, Group Policy overrides the Settings toggle. On the target PC, run gpedit.msc and navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections. Double-click “Allow users to connect remotely using Remote Desktop Services” and set it to Enabled. Also check “Restrict Remote Desktop Services users to a single Remote Desktop Services session”—if it’s enabled, you can’t have multiple sessions. If the machine is part of a domain, the policy may be set by the server; contact your administrator. A registry edit can also force-enable: under HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server, set fDenyTSConnections to 0. Always back up the registry before editing.

Frequently Asked Questions

Why does Remote Desktop say “can’t connect” even though I can ping the computer?

Ping only proves the host is on the network. The RDP port (3389) may still be closed, the service may be stopped, or the firewall may be blocking it. Use telnet <IP> 3389 from the client to test the port. If telnet connects (blank screen), the port is open; if it fails, the issue is on the host’s firewall or service.

Can I connect to a Windows 10 Home edition via Remote Desktop?

No, Windows Home editions do not include the Remote Desktop host (the ability to accept incoming RDP connections). You can use the Remote Desktop client to connect to Pro/Enterprise machines, but to connect to a Home PC, you’ll need third-party software like TeamViewer, AnyDesk, or VNC.

What does “The remote computer is not available on the network” mean?

This usually means the host is powered off, asleep, or not connected to the same network. It can also mean the IP address changed (DHCP lease expired) or the host is behind a firewall that drops all traffic. Check the host’s power state and IP, and consider setting a static IP or using the computer name with DNS.

How do I change the Remote Desktop port from 3389 to something else?

You can change the port via registry: on the host, go to HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp and modify the PortNumber DWORD value to your desired port (e.g., 3390). Then restart the Remote Desktop Services. On the client, connect to IP:port (e.g., 192.168.1.100:3390). This can reduce automated attacks but isn’t a substitute for a VPN.

Why does Remote Desktop work on LAN but not over the internet?

Most likely the router isn’t forwarding port 3389 to the host’s local IP, or your public IP is dynamic. Also, your ISP may block inbound ports. Check the router’s port forwarding settings, and consider using a VPN or a Remote Desktop Gateway for a secure connection.

Is it safe to enable Remote Desktop on my PC?

It’s safe if you use a strong password, keep Windows updated, and don’t expose port 3389 directly to the internet. Use Network Level Authentication, and prefer connecting via a VPN or a Remote Desktop Gateway. Disable it when you don’t need it—the attack surface isn’t worth the convenience for most home users.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →