Remote Desktop client cannot establish connection with Remote Computer Solution

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:
This is because the registry certificate sub-key is responsible for the authentication and encryption of data information in the terminal service communication. Once it is 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 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 locate

HKLM \ SOFTWARE \ Microsoft \ mslicensing.
2. Back up the mslicensing key.
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" to the current Login 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" = "{4d36e97d-e325-11ce-bfc1-08002be10318 }"
"Class" = "system"

"Hardwareid" = hex

(7):, 4f, 00, 4f, 00, 00, 5C, 00, 00, 00
"Driver" = "{4d36e97d-e325-11ce-bfc1-08002be10318 }\\ 0030"
"MFG" = "(standard system device )"
"Service" = "rdpdr"
"Devicedesc" = "Terminal Server Device redirection"
"Configflags" = DWORD: 00000000
"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.

Service end.

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); "Remote Desktop" on the "remote" page in system properties is not checked or is not used

Users with the remote logon permission. You can directly check the remote logon permission. for users with the remote login permission, you need to add the relevant account in "select remote user;
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.