You enter the computer name in Remote Desktop Connection, select Connect, and expect the other computer’s desktop to appear. Instead, Windows displays an error saying it can’t connect to the remote computer.
This error does not always mean Remote Desktop is broken. The target computer might be offline, Windows might be blocking incoming connections, the computer name might not resolve correctly, or your network might not allow Remote Desktop traffic.
The important thing is to identify where the connection is failing before changing settings unnecessarily.
In this guide, you will learn how to troubleshoot Remote Desktop connection failures on Windows 11 and Windows 10. The steps cover computer availability, network connectivity, firewall rules, account permissions, Network Level Authentication, and more advanced checks.
First, Identify What Is Preventing the Connection
Before changing anything, pay attention to when the error appears.
Remote Desktop problems generally fall into three categories:
- Connection errors: Windows cannot locate or establish a connection to the remote computer.
- Authentication errors: Windows reaches the computer, but your account credentials or permissions are rejected.
- Session errors: The connection begins but fails before the remote desktop becomes usable.
For example, an error saying that Remote Desktop cannot connect because the computer is turned off points toward availability or network access. A message about credentials points toward a sign-in problem instead.
Start with the following checks before moving to more advanced solutions.
1. Make Sure the Remote Computer Is Turned On and Awake
This is one of the easiest problems to overlook.
Remote Desktop cannot establish a normal connection to a computer that is powered off, sleeping, or disconnected from the network.
Check the computer you are trying to access:
- Make sure it is powered on.
- Confirm that it has an active Wi-Fi or Ethernet connection.
- Check whether it has entered Sleep or Hibernate mode.
- If possible, restart the computer.
- Try connecting again.
If the remote computer is physically accessible, check its display and network connection rather than assuming it is available simply because it was working earlier.
You should also review its power settings if you regularly access it remotely.
On Windows 11:
- Open Settings.
- Select System.
- Choose Power & battery.
- Expand Screen and sleep.
- Review when the computer enters sleep mode.
On Windows 10, open Settings > System > Power & sleep.
You can adjust the sleep settings to keep the computer available when you need remote access. Consider the device’s power consumption and security requirements before preventing sleep indefinitely.
2. Check Whether Remote Desktop Is Enabled on the Target PC
The computer you want to control must be configured to accept incoming Remote Desktop connections.
This is different from opening Remote Desktop Connection on your own computer. Launching the client does not automatically enable remote access on the other device.
On the target computer:
- Press Windows + I.
- Open System.
- Select Remote Desktop.
- Check whether Enable Remote Desktop is switched on.
- If it is off, turn it on and confirm the change.
Also check the Remote Desktop users list if you are connecting with a non-administrator account.
Important: Windows Home editions can initiate Remote Desktop connections but cannot host incoming standard Microsoft Remote Desktop sessions. If the computer you want to control runs Windows 11 Home or Windows 10 Home, you will need a supported Windows edition or another remote-access solution.
If you cannot find the Remote Desktop hosting option, check the Windows edition before attempting other fixes.
3. Verify the Computer Name or Try Its IP Address
An incorrect computer name can prevent Windows from locating the remote device.
Even when you enter the correct name, your network might not be able to resolve it through DNS or local name resolution.
First, verify the computer name on the remote PC:
- Open Settings.
- Select System.
- Choose About.
- Find Device name under Device specifications.
Compare the name with the value entered in Remote Desktop Connection.
If it still fails, try connecting with the remote computer’s IP address.
On the target computer:
- Press Windows + R.
- Type
cmd. - Press Enter.
- Run:
ipconfig- Find the active network adapter.
- Look for its IPv4 Address.
For example, the address might look like 192.168.1.105.
Return to your own computer, open Remote Desktop Connection, and enter that IP address in the Computer field instead of the device name.
If the IP address works but the computer name does not, the problem is likely related to name resolution rather than Remote Desktop itself.
Remember that private IP addresses can change when a router assigns a new address. For a computer you access regularly, a DHCP reservation can help keep its local address consistent.
4. Check Whether Both Computers Can Communicate Over the Network
Remote Desktop needs a working network path between the computer initiating the connection and the computer receiving it.
If both devices are on the same home or office network, confirm that they are connected to the appropriate network.
If they are on different networks, you need a properly configured remote network connection, such as a VPN.
You can perform a basic connectivity check using Command Prompt.
On your computer, open Command Prompt and enter:
ping 192.168.1.105Replace the example address with the remote computer’s actual IP address.
If you receive replies, the target computer is responding to ICMP traffic.
If you receive a timeout, it does not automatically prove that the computer is offline. Windows Firewall or another network device might block ping requests even when the computer is available.
Use the next test to check the Remote Desktop connection itself.
5. Test Whether the Remote Desktop Port Is Reachable
Remote Desktop normally uses TCP port 3389. If a firewall or network device blocks this traffic, Windows may fail to establish a connection even when both computers are online.
PowerShell includes a command that can test whether the port is reachable.
On the computer you are connecting from:
- Right-click Start.
- Open Terminal or PowerShell.
- Enter the following command:
Test-NetConnection -ComputerName 192.168.1.105 -Port 3389Replace 192.168.1.105 with the remote computer’s IP address.
Look for the TcpTestSucceeded result.
If TcpTestSucceeded is True: The TCP connection to that port succeeded. This suggests that the network path and port are reachable, although it does not prove that authentication or the Remote Desktop session will work.
If TcpTestSucceeded is False: The connection to that port failed. Check whether Remote Desktop is enabled, whether the target computer is listening for connections, and whether a firewall or network device is blocking the traffic.
Do not assume that disabling Windows Firewall is the solution. Identify which rule or network restriction is responsible first.
6. Check Windows Firewall for Blocked Remote Desktop Connections
Windows Firewall can prevent incoming Remote Desktop connections when the appropriate rules are disabled or do not apply to the current network profile.
You can inspect the rules through Windows Defender Firewall with Advanced Security.
On the remote computer:
- Press Windows + R.
- Type
wf.msc. - Press Enter.
- Select Inbound Rules.
- Find the rules associated with Remote Desktop.
- Check the Remote Desktop – User Mode (TCP-In) rule.
- Confirm that it is enabled for the appropriate network profile.
The corresponding UDP rule may also be used for Remote Desktop traffic.
If the TCP rule is disabled, right-click it and select Enable Rule, provided that allowing Remote Desktop on that network is appropriate.
Also check the network profile.
If you are connecting over a trusted home or office network, Windows should generally recognize it as a Private network. Do not change an untrusted public network to Private simply to make Remote Desktop work.
Avoid turning off the entire firewall. It protects your computer against other unwanted network connections.
7. Confirm That Your Windows Account Has Remote Access Permission
Sometimes Remote Desktop reaches the target computer but refuses to sign you in.
This can happen when you use an account that has not been granted permission to access the remote PC.
On the target computer:
- Open Settings.
- Select System.
- Choose Remote Desktop.
- Open Remote Desktop users.
- Check whether the account you intend to use is listed.
Administrators generally have permission by default, while standard users may need to be added.
You should also check that you are entering the correct credentials.
The username and password belong to an account on the remote computer. They are not necessarily the same as the account you use on your current device.
If the remote PC uses a Microsoft account, make sure you are using the appropriate account credentials rather than assuming your Windows Hello PIN will work as the Remote Desktop password.
If you previously saved incorrect credentials, open Credential Manager in Windows and check the relevant saved Windows credentials. Update or remove outdated entries before trying again.
8. Check Network Level Authentication (NLA)
Network Level Authentication is a security feature that requires users to authenticate before Windows establishes a full Remote Desktop session.
It helps protect the remote computer by preventing unauthenticated users from reaching the sign-in stage of a session.
However, compatibility problems can occur when an older Remote Desktop client does not support the authentication requirements configured on the target computer.
First, make sure the Remote Desktop client is up to date.
If you are using a supported but older device, check whether its Remote Desktop client supports Network Level Authentication.
You can inspect the setting on the target PC:
- Open Settings.
- Select System.
- Choose Remote Desktop.
- Expand the Remote Desktop settings if necessary.
- Locate the option requiring Network Level Authentication.
Keep this security requirement enabled whenever possible.
Disabling NLA should not be your first troubleshooting step. Only consider a temporary change when you have confirmed a compatibility issue and understand the security implications. Restore the protection as soon as the compatibility problem is resolved.
9. Restart Remote Desktop Services and Check for Windows Problems
If the previous checks do not resolve the issue, the Remote Desktop service itself may not be operating correctly.
On the target computer:
- Press Windows + R.
- Type
services.msc. - Press Enter.
- Find Remote Desktop Services.
- Check its status.
If the service is stopped, investigate why it is not running. On a normally configured supported Windows PC, Remote Desktop Services should be available when the feature is in use.
If appropriate, right-click the service and select Restart.
You can also restart the computer to reload its services and network configuration.
Do not randomly change registry entries or service startup settings. Advanced Remote Desktop listener problems can involve system configuration, and incorrect changes may make remote access harder to restore.
If you are troubleshooting a managed business computer or Windows Server, involve the administrator before changing service, domain, or policy settings.
What Different Remote Desktop Errors Usually Mean
The wording of the error can help narrow down the problem.
| Error or symptom | What to investigate |
|---|---|
| Remote Desktop can’t connect to the remote computer | Remote access, network, firewall and target availability |
| The remote PC can’t be found | Computer name, DNS or IP address |
| Remote Desktop connection timed out | Network path, firewall or unavailable device |
| Your credentials did not work | Username, password and account permissions |
| The connection was denied | Remote Desktop permissions or security policy |
| Remote Desktop is not enabled | Windows edition and remote access configuration |
Do not apply every fix to every error. For example, changing firewall settings will not correct an incorrect password, and resetting credentials will not bring an offline computer back onto the network.
Frequently Asked Questions
Why does Remote Desktop say it can’t connect to the remote computer?
The remote PC might be turned off, sleeping, disconnected from the network, or not configured to accept incoming connections. Firewall restrictions, incorrect computer names and network problems can also cause this error.
Why does Remote Desktop work with an IP address but not the computer name?
This usually points to a name-resolution problem. Your network can reach the computer by its IP address but cannot correctly resolve its hostname. Check DNS or local network name resolution.
Does Remote Desktop require both computers to use the same Wi-Fi?
No. Both computers can use different networks, but you need a secure and properly configured connection between them. A VPN is a suitable option for accessing a home or office network remotely.
Can Windows 11 Home accept incoming Remote Desktop connections?
No. Windows 11 Home can act as a Remote Desktop client, but it cannot host incoming standard Microsoft Remote Desktop sessions. The target computer needs a supported edition such as Pro, Enterprise or Education.
What port does Windows Remote Desktop use?
Remote Desktop normally uses TCP port 3389. However, an administrator can configure a different listening port, so check the target computer’s configuration if the standard port test fails.
Why can I connect to the remote computer but cannot sign in?
The computer may be reachable, but the account credentials could be incorrect or the account may not have permission to use Remote Desktop. Check the username, password and Remote Desktop users list.
Should I disable Windows Firewall to fix Remote Desktop?
No. Disabling the entire firewall exposes your computer to unnecessary risk. Check the specific Remote Desktop inbound rules and allow connections only on trusted, appropriate network profiles.
