RDP Error occurred: This PC cannot be connected to REMOTE COMPUTER

The issue resembles this: when you attempt to connect with a distant/remote Windows worker/work area through RDP, the mstsc.exe client freezes, and a window with the accompanying RDP failure shows up:

Check RDP network connectivity

Most importantly, check if the distant PC is accessible from your gadget over the network, and the default Remote Desktop port (TCP 3389) is reacting (and not impeded by firewalls).

Ensure the DNS address of the distant RDP host is effectively settled from your PC. Utilize the commands given below

nslookup rdp_server_name1 
ping rdp_server_name1

In the event that the DNS name isn’t resolved as expected, look at your DNS settings to try associating with a remote host utilizing an IP address.

You can check the RDP port accessibility on a remote server from a clients workstation utilizing:

The Telnet client:

telnet rdp_server_name1 3389

PowerShell 4.0 and higher:

Test-NetConnection rdp_server_name1 -Port 3389 -InformationLevel Quiet

PowerShell all versions:

New-Object System.Net.Sockets.TcpClient).Connect(‘rdp_server_name1’, 3389)

In case port 3389 is not available, check if the Remote Connection is enabled on the remote server (right-click on Start button > Settings > System > Remote Desktop > Enable Remote Desktop).

Check RDP service settings on the remote computer

if that Remote Desktop is enabled, next you should check the setting which decides the most extreme number of synchronous clients’ associations with a Remote Desktop. Open tsadmin.msc mmc snap-in (Administrative instruments > Remote Desktop Services > Remote work area Session Host Configuration). click RDP-TCP properties, and check the value of the Maximum connections property in Network Adapter tab

The tsadmin.msc is not available t in current Windows renditions (like Windows 10 or Windows Server 2016), so you should set the RDP administration settings utilizing Group Policies.

Open the nearby GPO editorial manager on the remote host: Win + R > gpedit.msc

Explore to the accompanying GPO segment: Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections

Empower the arrangement boundary named Allow clients to interface distantly utilizing Remote Desktop Services (if this strategy is off, the far off client can not connect with this PC utilizing Remote Desktop Services)

Additionally, check if the Remote Desktop Services don’t restrict the number of synchronous associations with the worker. The greatest number of RDP associations can be indicated in the part Connections utilizing the arrangement Limit number of associations. Set limitless connections by indicating 999999 in the choice RD Maximum Connections permitted;

Utilize the netstat order to check if TCP port 3389 is in the Listening state. Open a command prompt as administrator, and execute the command:

netstat -a -o|find "LIST"

In our example, 3389 port is listening


Attempt to restart the Remote Desktop Services administration. You can perform this activity utilizing the services.msc console or with the accompanying command in the PowerShell brief:

get-service TermService| Restart-Service -force -Verbose

Take a look at RDP Port and Windows Firewall Settings

Sometimes the administrator can change the RDP port number from default 3389 to something different (despite the fact that Microsoft doesn’t suggest this). To check the current port on which the Remote Desktop administration is tuning in on the PC, open the library editorial manager (regedit.exe), and go to the vault key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp

Note the value of the PortNumber REG_DWORD boundary. It shows the current TCP port allocated to the RDP administration. In our model, this is 3389 (d3d hexadecimal worth). If have an alternate port, you can transform it to 3389 (in decimal), and restart the PC.

Likewise, make sure that the standard permitting approaching RDP associations is empowered in the Windows Firewall settings.

To do this, go to the Control Panel\System and Security\Windows Defender Firewall;

Press the “Permit an application or component through Windows Defender Firewall” > Change Settings;

Track down the Remote Desktop rule, and ensure it is empowered for Private and Public organizations

If you utilize an outsider firewall or antivirus, ensure it doesn’t obstruct approaching RDP associations. You can briefly impair your antivirus programming.

Then, check your network connection properties. Confirm the network association status is set to Public. Change it from Private to Public if necessary (Settings > Network and Internet > Status > Network status > Change connection properties.

at times, you need to resetting the winsock and ip stack settings for the network connector on the remote PC. Open a command with executive rights and run the orders:

netsh winsock reset

netsh int ip reset

ipconfig /release

ipconfig /renew

ipconfig /flushdns

In Windows 10, there is a option to reset network settings in Settings > Network and Internet > Status > Network reset.

After resetting the network settings reboot Windows.

RDP this computer is unable to connect to remote PC: Possible reason

One more conceivable reason for the RDP mistake might be an undeniable degree of safety, which isn’t upheld by more established adaptations of the RDP customer.

For this situation, open the General tab on the RDP-Tcp properties window, and change the Security layer from default Negotiate to less get RDP Security Layer.

Key hint: Snap-in tsadmin.msc and RDP-Tcp Properties discourse encloses are missing Windows Server 2019/2016 and 2012 R2. Yet, you can arrange the Remote Desktop setting utilizing the nearby Group Policy Editor (gpedit.msc). The vital strategies are situated in the accompanying GPO segment: Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.

RDP security level can be indicated utilizing the arrangement named Require client of explicit security layer for remote (RDP) associations. Empower this strategy, and in the dropdown select the RDP Security level. This will change the Remote Desktop security layer from the default Negotiate to the less secure RDP.

Can’t connect to remote PC: Remote App disconnetected

Solve this problem perform the following steps on the RDP client:

Open Registry Editor (regedit.exe);

Click the registry key HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client;

Create a DWORD parameter with the name RDGClientTransport and the value 1;

Restart the computer.

The RDGClientTransport parameter forces the clients to use the RPC/HTTP connections instead of HTTP/UDP to connect to the server.

If the above solution didn’t fix the RDP connection error, try to change the collection settings on the RDSH server side. Open properties of your problematic application collection, go to the Security tab, and uncheck the option “Allow connections only from computers running Remote Desktop with Network Level Authentication”.

IF the RemoteApp Disconnected happens on only a single not-domain joined PC, it is conceivable, that the distinctive LAN Manager/NTLM strategy settings are utilized on the RDSH have and the personal computer. This can regularly mess confirmation up.

Check current Network Security: LAN Manager validation level approach settings on RSDH utilizing the order gpresult/r c:\tmp\gpreport.html (examine html document) or utilizing rsop.msc (this strategy is situated in the part Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options). In the event that LM and NTLMv1 conventions are incapacitated on your RDSH worker (Send NTLMv2 Response just approach esteem), you should change the suitable strategy settings on the customer side.

To do this, open the neighborhood GPO proofreader (gpedit.msc);

Go to the GPO segment above;

Enable the strategy “Network Security: LAN Manager verification level”, and set its worth to Send NTLMv2 Response as it were;

Solve: Can’t Connect to the Remote Desktop Gateway Server

this error may look like this:

To solve this problem:

  1. Go to Internet Information Services (IIS) Manager on the Remote Desktop Gateway server;
  2. Go to the IIS section Sites > Default Website > RDWeb > Pages > Application Settings;
  3. For the DefaultTSGateway value, enter the server’s FQDN public name of your RD Gateway server, and then restart the web services with the command:

Your RDGW certificate shouldn’t be expired

Check your SSC Info by:

 Server Manager > Remote Desktop Services > Collections > Your_Collection > Tasks > Edit Deployment Properties > Certificates > RD Gateway > View Details

Start the new RDP sesion on your client PC. Successfull connection will work.

Leave a Reply

Your email address will not be published. Required fields are marked *

Enter Captcha Here :