RDP error: This computer can’t connect to the remote computer
2017-06-02 16:01
274 查看
http://theitbros.com/this-computer-cant-connect-to-the-remote-computer/
![](http://theitbros.com/wp-content/uploads/2016/11/rdp_error_this_computer.jpg)
Telnet client:
PowerShell 4.0 and higher:
![](http://theitbros.com/wp-content/uploads/2016/11/powershell_TNC.jpg)
PowerShell all versions:
If port 3389 is unavailable, you should check that Remote Connections is enabled on the remote server (Right click on Start button-> System -> Remote settings -> Allow remote connections to this computer).
![](http://theitbros.com/wp-content/uploads/2016/11/allow_remote_connections.jpg)
If Remote Desktop is enabled, next you should to check setting, which determines the maximum number of simultaneously connection to a Remote Desktop. Open tsadmin.msc snap-in (Administrative tools -> Remote Desktop Services -> Remote desktop Session Host Configuration). Click on RDP-TCP properties and check the value of Maximum connections property in Network Adapter tab.
![](http://theitbros.com/wp-content/uploads/2016/11/rdp_tcp_properties.jpg)
Another possible cause of the RDP error may be a high level of security, which is not supported by older versions of the RDP client.
In this case on RDP-Tcp Properties dialog box open General tab and change Security layer from default Negotiate to less secure RDP Security Layer.
![](http://theitbros.com/wp-content/uploads/2016/11/rdp_security_layer-2.jpg)
Tip. Snap-in tsadmin.msc and RDP-Tcp Properties dialog box are missing in Windows Server 2012/2012 R2. But you can configure Remote Desktop setting using local group policy editor (gpedit.msc). The necessary policies are located in the following section: Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host.
RDP security level can be specify using policy named Require user of specific security layer for remote (RDP) connections. Enable this policy and in dropdown select RDP Security level.
![](http://theitbros.com/wp-content/uploads/2016/11/rdp_security_layer.jpg)
Maximum number of RDP connection can be specified in section Connections using policy Limit number of connections. Set unlimited connection by specify 999999 in the option RD Maximum Connections allowed
![](http://theitbros.com/wp-content/uploads/2016/11/rdp_limit_number_connections-1.jpg)
Go back to your client PC and try to start new RDP Session. The connection should be established successfully.
![](http://theitbros.com/wp-content/uploads/2016/11/rdp_error_this_computer.jpg)
This computer can’t connect to the remote computer
First of all, check that the remote computer is accessible over the network and the Remote Desktop port (TCP 3389) is responding. You can check port availability using:Telnet client:
telnet rdp_server_name1 3389
PowerShell 4.0 and higher:
Test-NetConnection rdp_server_name1 -Port 3389 -InformationLevel Quiet
![](http://theitbros.com/wp-content/uploads/2016/11/powershell_TNC.jpg)
PowerShell all versions:
New-Object System.Net.Sockets.TcpClient).Connect(‘rdp_server_name1’, 3389)
If port 3389 is unavailable, you should check that Remote Connections is enabled on the remote server (Right click on Start button-> System -> Remote settings -> Allow remote connections to this computer).
![](http://theitbros.com/wp-content/uploads/2016/11/allow_remote_connections.jpg)
If Remote Desktop is enabled, next you should to check setting, which determines the maximum number of simultaneously connection to a Remote Desktop. Open tsadmin.msc snap-in (Administrative tools -> Remote Desktop Services -> Remote desktop Session Host Configuration). Click on RDP-TCP properties and check the value of Maximum connections property in Network Adapter tab.
![](http://theitbros.com/wp-content/uploads/2016/11/rdp_tcp_properties.jpg)
Another possible cause of the RDP error may be a high level of security, which is not supported by older versions of the RDP client.
In this case on RDP-Tcp Properties dialog box open General tab and change Security layer from default Negotiate to less secure RDP Security Layer.
![](http://theitbros.com/wp-content/uploads/2016/11/rdp_security_layer-2.jpg)
Tip. Snap-in tsadmin.msc and RDP-Tcp Properties dialog box are missing in Windows Server 2012/2012 R2. But you can configure Remote Desktop setting using local group policy editor (gpedit.msc). The necessary policies are located in the following section: Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host.
RDP security level can be specify using policy named Require user of specific security layer for remote (RDP) connections. Enable this policy and in dropdown select RDP Security level.
![](http://theitbros.com/wp-content/uploads/2016/11/rdp_security_layer.jpg)
Maximum number of RDP connection can be specified in section Connections using policy Limit number of connections. Set unlimited connection by specify 999999 in the option RD Maximum Connections allowed
![](http://theitbros.com/wp-content/uploads/2016/11/rdp_limit_number_connections-1.jpg)
Go back to your client PC and try to start new RDP Session. The connection should be established successfully.
相关文章推荐
- The Visual Studio Remote Debugger service on the target computer cannot connect back to this computer
- The Visual Studio Remote Debugger service on the target computer cannot connect back to this computer
- Can't connect to remote MySQL server with error 61
- error 18483: could not connect to server 'dalian' because 'distributor_admin' is not defined as a remote login at the server.
- Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a
- Mongo connecting error Failed to connect to: *.*.201.18:27018: Remote server has closed the conne
- To log onto this remote computer, you must be granted the Allow Log on through Terminal Services Right.
- 总结ERROR 2002 (HY000):Can't connect to...之错误
- 总结ERROR 2002 (HY000):Can't connect to...之错误
- 【转】Vmware ESX 3.0出现“error connecting: can not connect to host x.x.x.x: a connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed……的解决方法
- ERROR 1130: Host 'A'is not allowed to connect to this MySQL server
- SVN错误:Error: Can't connect to host ''
- 关于错误“Cannot connect to the Citrix MetaFrame server.Can't assign requested address”的解决方法
- Unable to create this part due to an internal errorReason for the failure An unexpected exception was thrown
- The call to LoadLibrary(YourExtensionName) failed, Win32 error 0n14001, “This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.”
- (zt)ERROR 1130: Host '192.168.1.110' is not allowed to connect to this MySQL server
- ExtractionError: Can't extract file(s) to egg cache The following error occurred while trying to extract file(s) to the
- ERROR 1130: Host 'A'is not allowed to connect to this MySQL server
- Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.