RDP Error: This Computer Can’t Connect To The Remote Computer
Let’s attempt to find out the way to fix an RDP connection error. This computer can’t hook up with the remote computer. It occurs once you attempt to hook up with a foreign computer or Remote Desktop Server (RDS) using the built-in Windows RDP client (mstsc.exe).
The problem seems like this: once you attempt to hook up with a foreign Windows server/desktop via RDP, the mstsc.exe client freezes for a moment, and a window with the subsequent RDP error appears:
Remote Desktop Connection
This computer can’t hook up with the remote computer.
Try connecting again. If the matter continues, contact the owner of the remote computer or your network administrator.
Check the RDP Network Connectivity
First of all, check if the remote computer is accessible from your device over the network, and therefore the default Remote Desktop port (TCP 3389) is responding (and not blocked by firewalls).
Make sure the DNS address of the remote RDP host is correctly resolved from your computer. Use the subsequent commands:
nslookup rdp_server_name1 ping rdp_server_name1
If the DNS name isn’t resolved properly, check your DNS settings or try connecting to a foreign host using an IP address.
You can check the RDP port availability on a foreign server from a client workstation using:
The Telnet client:
telnet rdp_server_name1 3389
PowerShell 4.0 and higher:
Test-NetConnection rdp_server_name1 -Port 3389 -InformationLevel Quiet
Note. If this command returned True, then the RDP port responds on the server and it’s not blocked.
PowerShell all versions:
New-Object System.Net.Sockets.TcpClient).Connect(‘rdp_server_name1’, 3389)
If port 3389 is unavailable, you should check if the Remote Connection is enabled on the remote server (right-click on Start button > Settings > System > Remote Desktop > Enable Remote Desktop).
You can remotely enable Remote Desktop on a Windows computer by changing the fDenyTSConnections registry.
Check the RDP Service Settings on the Remote Computer
If Remote Desktop is enabled, next you ought to check the setting which determines the utmost number of simultaneous users’ connections to a foreign Desktop. Open tsadmin.msc mmc snap-in (Administrative tools > Remote Desktop Services > Remote desktop Session Host Configuration). Click on RDP-TCP properties, and check the worth of the utmost connections property in the Network Adapter tab.
The tsadmin. msc is missing in modern Windows versions (like Windows 10 or Windows Server 2016), so you ought to set the RDP service settings using Group Policies.
- Open the local GPO editor on the remote host: Win + R > gpedit.msc
- Navigate to the subsequent GPO section: Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections
- Enable the policy parameter named Allow users to attach remotely using Remote Desktop Services (if this policy is disabled, the remote user won’t be ready to hook up with this computer using Remote Desktop Services);
- Also, check if the Remote Desktop Services do not limit the number of simultaneous connections to the server. A maximum number of RDP connections can be specified in the section Connections using the policy Limit number of connections. Set unlimited connections by specifying 999999 in the option RD Maximum Connections allowed;
Use the netstat command to verify if TCP port 3389 is Listening. Open a command prompt as administrator, and execute the command:
netstat -a -o|find "LIST"
As you can see, in our example, port 3389 is listening.
TCP 0.0.0.0:3389 DESKTOP-JOPF9:0 LISTENING 1096
Try to restart the Remote Desktop Services service. You can perform this action using the services.msc console or with the following command in the elevated PowerShell prompt:
get-service TermService| Restart-Service -force -Verbose
Check RDP Port and Windows Firewall Settings
In some cases, the administrator can change the RDP port number from default 3389 to something else (although Microsoft doesn’t recommend this). To see the present port on which the Remote Desktop service is listening on the pc, open the registry editor (regedit.exe), and attend the registry key:
Note the worth of the PortNumber REG_DWORD parameter. It indicates the present TCP port assigned to the RDP service. In our example, this is often 3389 (d3d hexadecimal value). If you’ve got a special port, you’ll change it to 3389 (in decimal), and restart the pc.
Also, make sure the rule allowing incoming RDP connections is enabled within the Windows Firewall settings.
- To do this, attend the Control Panel\System and Security\Windows Defender Firewall;
- Press the “Allow an app or feature through Windows Defender Firewall” > Change Settings;
- Find the Remote Desktop rule, and confirm it’s enabled for personal and Public networks.
If you employ a third-party firewall or antivirus, confirm it doesn’t block incoming RDP connections. you’ll temporarily disable your antivirus software.
Next, check your network connection properties. Verify the network connection status is about to be Public. Change it from Private to Public if needed (Settings > Network & Internet > Status > Network status > Change connection properties).
In some cases, you would like to undertake to reset the Winsock and IP stack settings for the network adapter on the remote computer. Open a prompt with administrator rights and run the commands:
netsh winsock reset netsh int ip reset ipconfig /release ipconfig /renew ipconfig /flushdns
In Windows 10, there is a special option to reset network settings in Settings > Network and Internet > Status > Network reset.
After resetting the network settings, you need to reboot Windows.
RDP This computer can’t connect to the remote computer: a possible cause
Another possible explanation for the RDP error could also be a high level of security, which isn’t supported by older versions of the RDP client.
In this case, open the overall tab on the RDP-Tcp properties window, and alter the safety layer from default Negotiate to less secure RDP Security Layer.
Tip. Snap-in tsadmin.msc and RDP-Tcp Properties dialog boxes are missing in Windows Server 2019/2016 and 2012 R2. But you’ll configure the Remote Desktop setting using the local Group Policy Editor (gpedit.msc). the required policies are located within the following GPO section: Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.
RDP security levels are often specified using the policy named Require user of specific security layer for remote (RDP) connections. Enable this policy, and within the dropdown select the RDP Security level. this may change the Remote Desktop security layer from the default Negotiate to the less secure RDP.
RemoteApp Disconnected: Can’t Connect to the Remote Computer
In some cases, when connecting with Windows 10 to a foreign desktop on Remote Desktop Gateway on Windows 2012 R2, a mistake occurs:
Your computer can’t hook up with the remote computer because a mistake occurred on the remote computer that you simply want to attach to. Contact your network administrator for assistance.
To fix this problem, you would like to perform the subsequent steps on the RDP client:
- Open the Registry Editor (regedit.exe);
- Go to the registry key HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client;
- Create a DWORD parameter with the name RDGClientTransport and therefore the value 1;
Restart the pc.
The RDGClientTransport parameter forces the clients to use the RPC/HTTP connections rather than HTTP/UDP to attach to the server.
If the above solution didn’t fix the RDP connection error, attempt to change the gathering settings on the RDSH server side. Open properties of your problematic application collection, attend the safety tab, and uncheck the choice “Allow connections only from computers running Remote Desktop with Network Level Authentication”.
If the RemoteApp Disconnected error occurs on only one not-domain joined computer, it’s possible, that the various LAN Manager/NTLM policy settings are used on the RDSH host and therefore the personal computer. this will often cause authentication problems.
Check current Network Security: LAN Manager authentication level policy settings on RSDH using the command gpresult /r c:\tmp\gpreport.html (inspect html file) or using rsop.msc (this policy is found within the section Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options). If LM and NTLMv1 protocols are disabled on your RDSH server (Send NTLMv2 Response only policy value), you want to change the acceptable policy settings on the client side.
- To do this, open the local GPO editor (gpedit. msc);
- Go to the GPO section above;
- Enable the policy “Network Security: LAN Manager authentication level”, and set its value to Send NTLMv2 Response only;
- Update the policies on the client with the command gpupdate;
- Check your RemoteApp connection.
Fix: Can’t Connect to the Remote Desktop Gateway Server
There is another error related to Remote Desktop Gateway, on which users run RemoteApps.
Your computer can’t hook up with the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect. A valid Remote Desktop Gateway server address.
This error looks like this:
Your computer can’t hook up with the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance.
If you’re facing one among the errors above, then presumably the matter is your computer can’t resolve the general public FQDN name of your Remote Desktop Gateway server. In some cases, the general public RDGW name can’t match the hostname.
To fix this problem:
- Open the web Information Services (IIS) Manager on the Remote Desktop Gateway server;
- Go to the IIS section Sites > Default Website > RDWeb > Pages > Application Settings;
- For the DefaultTSGateway value, enter the server’s FQDN public name of your RD Gateway server, then restart the online services with the command:
Also, check your RDGW certificate. Your certificate must not be expired.
You can find your SSL certificate info by getting to Server Manager > Remote Desktop Services > Collections > Your_Collection > Tasks > Edit Deployment Properties > Certificates > RD Gateway > View Details. Check the certificate expiration date.
Go back to your client’s PC, and try to start a new RDP session. The connection should be established successfully.
Mustafa Al Mahmud is the Founder and CEO of Gizmo Concept and also a professional Blogger, SEO Professional as well as Entrepreneur. He loves to travel and enjoy his free moment with family members and friends.