Remote Connection Not Made: Causes and Fixes

Updated 7 November 2026 · Standard formula, shown below

The remote connection was not made because the client and the host could not establish a network path or complete the authentication handshake. This usually stems from an incorrect address, a blocked port, a disabled service, or a firewall rule, and it can be fixed by checking each layer in order.

What Does the Error Mean?

When you see “The remote connection was not made” on Windows, it means the Remote Desktop client (mstsc.exe) sent a connection request but never received the expected response from the target computer. The message is generic: it does not tell you whether the problem is a wrong IP address, a closed port, a credential issue, or a network outage. You have to diagnose it yourself.

This error appears in several variants: “The remote connection was not made because the name of the remote computer could not be resolved,” “The remote connection was not made because the remote computer is not reachable,” and “The remote connection was not made because the remote computer is not responding.” Each variant points to a different layer of the connection stack, but the underlying troubleshooting steps overlap.

How Remote Desktop Connections Work

Remote Desktop Protocol (RDP) is a proprietary protocol from Microsoft that lets you control another Windows computer over a network. The client sends a TCP packet to the host’s IP address on port 3389 (the default). The host, if it is listening, responds with a certificate and negotiates encryption. After that, you enter credentials and get a desktop session.

For the connection to succeed, four things must be true:

The host is powered on and not in sleep/hibernate mode.
The host has Remote Desktop enabled (Settings > System > Remote Desktop).
The host’s firewall allows inbound RDP traffic (TCP 3389).
The client can reach the host over the network (same LAN or via VPN/port forwarding).

If any one of these fails, you get the generic error. The most common cause is actually the firewall, because Windows Firewall prompts you when you enable Remote Desktop, and if you click “Cancel” or use a third-party firewall, the rule is never created.

Step-by-Step Troubleshooting

Work through these steps in order. Stop when the problem is solved.

Check the hostname/IP address. On the host, run ipconfig and note the IPv4 address. On the client, try pinging that address: ping 192.168.1.100. If ping fails, the host is off, on a different subnet, or a firewall is blocking ICMP.
Verify Remote Desktop is enabled. On the host, go to Settings > System > Remote Desktop and ensure the toggle is ON. Also check that the user account is in the Remote Desktop Users group (or is an administrator).
Test the port. From the client, run Test-NetConnection 192.168.1.100 -Port 3389 in PowerShell. If it returns TcpTestSucceeded : False, the port is closed or filtered.
Check the firewall. On the host, open Windows Defender Firewall > Advanced Settings > Inbound Rules. Look for “Remote Desktop” rules. They should be Enabled and set to Allow. If missing, create a new rule for TCP port 3389.
Restart the Remote Desktop services. On the host, open Services.msc, find “Remote Desktop Services” and “Remote Desktop Configuration.” Restart them. Also check that the “Remote Desktop Services” service is set to Automatic.
Check the network path. If the host is behind a router, you need port forwarding on the router (TCP 3389) and a public IP. If you are on a VPN, verify the VPN is connected and the host is reachable via the VPN IP.

Common Causes and Their Fixes

Here are the typical culprits and how to resolve each:

Wrong IP or hostname: Double-check the spelling and the IP. Use the host’s computer name if you are on the same LAN, or the IP if you are not.
Firewall blocking port 3389: Temporarily disable the host’s firewall to test. If the connection succeeds, re-enable it and add an inbound rule for TCP 3389.
Remote Desktop disabled: Enable it in Settings. On Windows 10/11 Home, Remote Desktop is not available; you need Pro or Enterprise.
Network Level Authentication (NLA) mismatch: If the client does not support NLA (older Windows), you may need to disable NLA on the host (but this is less secure).
Host is asleep: Disable sleep/hibernate on the host, or set Wake-on-LAN.
VPN not connected: If you are trying to connect from outside your LAN, you must use a VPN or port forwarding. A VPN is safer.

How to Choose the Right Fix

Match the error message to the likely cause:

“Name could not be resolved” → DNS or hostname issue. Use the IP address instead, or fix DNS.
“Remote computer is not reachable” → network path issue. Ping the host, check the router, VPN, or firewall.
“Remote computer is not responding” → the host is up but not listening on 3389. Check Remote Desktop service and firewall.
“The connection was denied” → credentials or permissions. Verify the user is in Remote Desktop Users.

If you are not sure, start with the port test. It tells you whether the problem is on the network or on the host.

Safety and Security Considerations

Exposing RDP directly to the internet is risky. Port 3389 is a common target for brute-force attacks. If you must access your computer remotely, use a VPN instead of port forwarding. If you do open the port, use a strong password, enable NLA, and consider changing the default port (though this is not a real security measure, just obscurity).

Also, be aware that Windows 10/11 Home edition does not support Remote Desktop as a host. You can only use it as a client. If you need to host, you need Pro, Enterprise, or Education.

Frequently Asked Questions

Why does the remote connection not made error appear even when the IP is correct?
Because the IP is only one part. The host may have Remote Desktop disabled, the firewall may block port 3389, or the Remote Desktop service may be stopped. Use the port test to isolate the issue.

Can I fix this by changing the port number?
Changing the port on the host (via registry) and the client (by appending :port) can bypass some firewalls that only block the default port, but it does not fix the underlying connectivity. It also does not improve security.

What does NLA mean and should I disable it?
Network Level Authentication requires the client to authenticate before a full remote session is created. It is more secure. Disable it only if you have a legacy client that does not support it, and only if you understand the risk.

Is there a way to test if port 3389 is open without using Remote Desktop?
Yes. Use PowerShell: Test-NetConnection <host> -Port 3389. If it shows TcpTestSucceeded : True, the port is open and the problem is likely elsewhere.

Why does the error say “name could not be resolved” when I use the IP?
That specific message appears when you type a hostname, not an IP. If you type an IP and get that error, it may be a DNS suffix issue. Try using the raw IP without any prefix.

Can I use Remote Desktop to connect to a computer that is turned off?
No. The host must be powered on and running. You can use Wake-on-LAN to turn it on, but that requires additional setup and the computer must be on the same LAN.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.