Solution for Remote Desktop client connection failure to remote computer

The client cannot establish a connection with a remote computer.
The possible cause of this error is:
1) the remote connection on the remote computer may not be enabled. 2) the maximum number of connections on the remote computer has been exceeded. 3) A network error occurred while establishing the connection.
Ii. Solution: www.2cto.com this is because the registry Certificate sub-key is responsible for the authentication and encryption of data information in Terminal Service Communications. Once damaged, the Protocol component of the Terminal Service will detect an error, interrupt communication between the client and the terminal server. There are many causes of damage to the Certificate subkey, such as the administrator's installation and uninstallation of some system software and unreasonable configuration of terminal service parameters. In this case, we need to reset the content in the key value to fix the terminal service. In the registry editor window, expand "HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ TermService \ Parameters", find the subkey named "Certificate", and delete it, restart the XP system or Windows 2000 Server, and the system will generate the "Certificate" subkey again, so that the client can connect to the terminal Server normally. When the terminal server cannot be connected, we must first determine whether this is caused by a network fault and check whether the remote client and Windows XP system (Windows Server server) can be normally connected to the network; then, check whether the encryption level of the terminal server is too high. After the above reasons are ruled out, the "Certificate" subkey may be corrupted. In addition, "X509 Certificate" and "X509 Certificate" under "HKEY_LOCAL _ MACHINE \ SYSTEM \ Cur logging ControlSet \ Services \ Term Service \ Parameters" may also cause terminal Service problems, they are repaired in the same way as when the "Certificate" sub-key is damaged. I spoke about it. I also attached several other remote connection error solutions to help you:
Solution: "The access permission of the local computer client cannot be upgraded or updated"
1. Open the Registry Editor of the controlled machine and go to HKLM \ SOFTWARE \ Microsoft \ MSLicensing. 2. Back up the MSLicensing key. Www.2cto.com 3. Delete the MSLicensing key and restart the system.
The message "the client cannot connect to a remote computer" is displayed ". Remote computers cannot be reached (cannot be pinged or blocked by the campus network firewall in the middle), the firewall of the controlled machine does not open the corresponding port, or the server is not enabled at all.
Solution to the prompt "remote computer connection ended"
1. Open the Registry Editor of the controlled machine, go to HKLM \ SYSTEM \ ControlSet001 \ Enum \ Root \ RDPDR, back up the item, right-click the item, and select "permission ", add "Full Control" permissions to the current logon user. 2. Create a new key file and write the following content. Double-click to import the registry and restart the computer. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE \ SYSTEM \ ControlSet001 \ Enum \ Root \ RDPDR \ 0000] "ClassGUID" = "{region}" "Class" = "System" "HardwareID" = hex (7) :, 4f, 00, 4f, 54, 00, 5c, 00 "Driver" = "{4D36E97D-E325-11CE-BFC1-08002BE10318 }\\ 0030" "Mfg" = "(standard system device) "" Service "=" rdpdr "" DeviceDesc "=" Terminal Server Device redirection "" ConfigFlags "= dword: 00000000 Www.2cto.com "Capabilities" = dword: 00000000 the system prompts "the client cannot connect to the remote computer". The remote computer cannot arrive (the ping fails or is blocked by the campus network firewall in the middle ), or the firewall of the controlled machine does not open the corresponding port, or the server is not enabled at all. Several other solutions that may cause problems:
The Terminal services Service is not started. Start this service (enter services in "run. msc can open the Service Manager). The remote desktop on the "remote" page in the system properties is not checked or the user with the remote login permission is not used. The former can be directly checked; in the "select remote user... "to add the relevant account; termsrv. the dll file may be damaged. You can copy one from the system32 directory of the same system to the safe mode (the file cannot be overwritten in normal mode unless the service is not started) and then overwrite the file; if the service is started, the user has set up, the file has been overwritten, and several methods have been tried, or not, you may have to reinstall the system. The author does not hate Xingchen