Cause analysis and resolution of problems caused by Remote Desktop inability to connect

Sometimes when a user makes a remote Desktop connection, they find that Remote Desktop is not connected and there are many reasons for this problem, so let's analyze the reasons why Remote Desktop cannot connect and how to solve it.

One, tips for "Local computer client Access License can not be upgraded or updated" solution

1, open the Registry Editor of the controlled machine, positioning to hklmsoftwaremicrosoftmslicensing.

2, Backup MSLicensing key.

3, delete the MSLicensing key, reboot the system.

Interrupt Remote Desktop Connection, the client cannot establish a connection to the remote computer

The possible causes of this error are:

1. Remote connections on the remote computer may not be enabled.

2, the maximum number of connections has been exceeded on the remote computer.

3, a network error occurred while establishing the connection.

Solution:

Sometimes this is the wrong hint: the connection was disconnected because of a network error, please reconnect to the remote computer; I must have opened the firewall, the 3389 port is also open, and connected to other servers can be connected, indicating that I do not have a problem with scanning software, scanned the server, Display IP and port are present, which means that the server network is no problem, there is no way, only continuous testing, and later in the system log saw a lot of system error messages.

Where: Critical Error The RDP protocol component "DATA encryption" found an error in the protocol stream and interrupted the client connection. "After all the trouble learned that this is because the certificate is responsible for Terminal Services communications in the authentication and encryption of data information, once it is corrupted, Terminal Services protocol components will detect errors, interrupt the client and Terminal Server communication. There are many reasons for the certificate, such as Administrator installation and uninstall of some system software, unreasonable configuration of Terminal Service parameters, etc. At this point we need to reset the contents of the key value in order to repair Terminal Services.

Enter the Registry Editor window, expand hkey_local_ma Chine systemcurrentcon trolsetservicestermservice parame ters, and locate the subkey named "Cer Tificate". Remove it, restart the XP system, or the Windows Certificate Server, and the system will regenerate the "child" subkey so that the client can connect to the terminal server properly.

After the terminal server has failed to connect, we first need to determine if this is a network failure, detect whether the remote client and XP system (Windows server servers) are able to connect to the network properly, and then check that the Terminal server's encryption level is set too high. After the above reasons are excluded, it is possible that the "certificate" subkey is corrupted.

In addition, "Serviceparameters X509" and "certificate" under "hkey_local _machine systemcur rentcontrolsetservicesterm X509" Certificate IDs may also cause problems with Terminal Services, and they are fixed in the same way that the "certificate" subkey is damaged.

Third, prompt "Client cannot connect to remote computer"

1, the remote computer can not be reached (ping or blocked by the firewall).

2, the server does not open 3389 ports (System Properties in the "remote" page of "Remote Desktop" does not tick or do not use a remote login permissions of users).

3, the Terminal Services service is not started, you can start this service, there are two RDP services also do not forget.

4, check the Remote Desktop is not changed the port, step: Open "Start → run", enter "regedit", open the registry, into the following path: [Hkey_local_machinesystem

Currentcontrolsetcontrolterminal Serverwdsrdpwdtdstcp], see Portnamber value? Its default value is 3389 if not, please change it back.

Four prompts the remote computer has ended the connection

1. Open the Registry Editor of the controlled machine, navigate to hklmsystemcontrolset001enumrootrdpdr, and back up the item; Right-click the item and select permissions to add Full control to the currently logged-on user.

2, create a new key file, write the following content, double-click the Import registry to restart the computer.

Windows Registry Editor Version 5.00

[hkey_local_machinesystemcontrolset001enumrootrdpdr000]

"Classguid" = "{4d36e97d-e325-11ce-bfc1-08002be10318}"

"Class" = "System"

"HardwareID" =hex (7): 52,00,4f,00,4f,00,54,00,5c,00,52,00,44,00,50,00,44,00,52,

00,00,00,00,00

"Driver" = "{4d36e97d-e325-11ce-bfc1-08002be10318}030"

"MFG" = "(Standard system device)"

"Service" = "rdpdr"

"DeviceDesc" = "Terminal Server Device Redirector"

"ConfigFlags" =dword:00000000

"Capabilities" =dword:00000000