Remote Desktop cant connect to the remote computer: Reasons and solutions
First, try to establish a session from a client that has been able to successfully connect in the past. A lack of a valid communications path can prevent a client from connecting to a remote desktop session. When the remote desktop connection between a Windows desktop and its host fails, it’s time to do some remote desktop troubleshooting by checking firewalls, security certificates and more. Services related to RDP should be running on both client and remote computers. Find the policy with name— Allow users to connect remotely by using Remote Desktop Services.
Check Your Firewall Rules
- When you establish a new Remote Desktop connection for the first time, the client saves the credentials for quick login.
- When the remote desktop connection between a Windows desktop and its host fails, it’s time to do some remote desktop troubleshooting by checking firewalls, security certificates and more.
- There can be multiple reasons, including permission, network, group policy, and more.
- If the issue persists, a Group Policy Object may be blocking the connection to your local computer.
- Adding the RDGClientTransport key tells the system to use RPC over HTTP, which can bypass network problems or security blocks affecting the default method.
When you save credentials for a specific remote computer and then try to connect to a different one, an error can occur because the saved credentials don’t match. Make sure to allow traffic on this port or list Remote Desktop as an allowed app to prevent the firewall from blocking access. Other factors, like network misconfigurations, DNS problems, or insufficient permissions, can also lead to this error.
Fix: You’ll need a new app to open this windowsdefender link
Having done that, check if you can connect through the remote desktop app. RDP uses Port number 3389, and if the connection is not getting established, make sure to check they are configured correctly on both the computer. Follow our exhaustive guide to check port restrictions on the Firewall to remove any firewall.
This update adjusts firewall settings to permit Remote Desktop. Change your network from “Public” to “Private” so Windows trusts other devices. This ensures Remote Desktop connects to the right machine, especially when network settings fail.
Enable Remote Desktop Services in Group Policy Editor
Use a reliable certificate authority to ensure that clients establish remote desktop connectivity. To avoid firewall problems, ensure that the port your remote desktop software uses is open on any firewalls residing between client computers and the server they connect to. It’s easy to dismiss the notion that a firewall could contribute to a remote desktop not working, but it’s quite common. In doing so, you might discover that the problem affects wireless connections but not wired ones. As a desktop admin, you can prevent and solve common remote desktop problems by using these tips. I hope you resolved the Remote desktop can’t connect to the remote computer problem.
Check whether a Group Policy Object (GPO) is blocking RDP on a local computer
- Updating the hosts file with the remote computer’s IP address can fix connection issues by making sure your computer links the remote’s name to its IP.
- If another application is using the RDP port, you have to find that application on the remote machine and then reconfigure it to use a port other than 3389.
- In Windows 10, you can choose to make your network profile Public or Private.
- The PowerShell command below lets you display the Windows Firewall state on the remote machine.
- You can email the site owner to let them know you were blocked.
This issue usually happens when Remote Desktop connections aren’t allowed on the remote system. If the firewall blocks port 3389 (RDP’s default port), connections won’t work. The most common causes are Remote Desktop being disabled on the target machine or incorrect firewall settings. This error indicates a configuration or network issue blocking the connection. I wrote this one mainly to compile all possible causes of failed RDP connections.
Change Your Network Profile
A quick reset of saved credentials can resolve this error. However, corrupt or changed credentials can often result in the Remote Desktop can’t connect to the remote computer error. On a Public network, Windows disables the network discovery feature to hide your computer from other computers.
Check whether a firewall is blocking the RDP port
If your user account has no administrator privileges, you should be a member of the local Remote Desktop Users group to access the remote machine via RDP. Keep in mind ping won’t work if ICMP is blocked on your network. You can use ping, a Telnet client, and PsPing from your local machine to check the connectivity to the remote computer. There are many reasons why an RDP connection to a remote machine might fail. This post aims to discuss all the common reasons why a Remote Desktop Protocol (RDP) connection can’t connect to a remote computer. Another workaround to fix Remote Desktop connection-related issues is to tweak the Registry Editor to add the RDGClientTransport key.
Network failure
One of the common reasons when your account does not have enough permission. Public networks block services like Remote Desktop, but setting it to private allows connections. Adding the RDGClientTransport key tells the system to use RPC over HTTP, which can bypass network problems or security blocks affecting the default method. Updating the hosts file with the remote computer’s IP address can fix connection issues by making sure your computer links the remote’s name to its IP.
Admins forced to troubleshoot a Microsoft RDP session stuck at configuration must understand these key steps to fix their issue and be able to adapt them to their environment. First, if remote desktops are going to connect properly, client computers must trust the certificate authority that issued the certificate. It’s also common for organizations to make it so that an RDP session can only be connected through a VPN. If you suspect the network might be to blame, try to narrow down the scope of the issue to find the root cause. The goal is to find out if the problem is specific to an individual client, the network or a terminal server/Windows server.
For Remote Desktop to work, services related to RDP should be running on both the remote and client systems. For your Remote Desktop Connection to work, the RDP Protocol must be enabled in the Registry. Manually adding the Remote PC address to the hosts file can help you resolve any issues that may occur because of domain name resolution. When you establish a new Remote Desktop connection for the first time, the client saves the credentials for quick login.
Check and Configure RDP Listen Port
In Windows 10, you can choose to make your network profile Public or Private. Check your Windows Defender Firewall settings to see if Remote Desktop Connection is blocked. Depending on how you have configured your firewall’s policy, it may block some inbound and outbound communications. As the PC restarts, turn on Remote Desktop again and check for any improvements. Follow our guide on how to enable and set up Remote Desktop Connection on Window 10 for further instructions.
If the Remote Desktop is already enabled, then turn it off and restart your PC. Before attempting any fixes in this article, make sure that Remote Desktop is enabled on your PC. Remote Desktop Connection allows you to connect to Remote Desktop enabled computers for troubleshooting and other purposes.
Here, you will have to manually enable the service using Group Policy Editor. If the issue persists, a Group Policy Object may be blocking the connection to your local computer. If the issue persists, verify the RDP listen port configuration in the Registry Editor.
Change/Tweak your Firewall Settings
The PowerShell command below lets you display the Windows Firewall state on the remote machine. If you can’t connect at all, a local firewall (Windows Firewall or third-party security software) or a network firewall might be blocking the port. If this works, and you are unable to ping the machine using the FQDN name, check whether DNS resolution is working properly. As you can see in the screenshot above, I was unable to ping the remote machine, and the port was not reachable as well. The main advantage of Telnet and PsPing is that you can connect via TCP, and you can check whether the RDP port 3389 is open. You can email the site owner to let them know you were blocked.
Permission and licensing issues
You can enable the Remote Desktop Connection either from System Properties or from the registry. Read this 4sysops article to learn how to add users remotely to a user group. By default, no members are in this group, and only members of the Administrators group can connect via RDP.
Try changing your network to Private to see if you can establish a connection with the network discovery feature enabled. When remote desktop credentials fail, admins should verify account format, cached credentials, lockout status, access permissions, firewall settings and DNS targeting. There can be multiple reasons, including permission, network, group policy, and more. Changing how Remote Desktop manages connections can often fix persistent issues. Allowing Remote Desktop ensures the system can accept remote access, solving a common connectivity issue.
Change Network Properties
It is also used to check a list of open ports on any computer. Sysinternals offer a PS Ping Tool to check if you can reach a com
