Cleverly solves the problem of Remote Desktop interruption

Remote Desktop is easy to use. You can use a Remote Desktop Connection Program to access the target computer. After you enter the user name and password, you can log on to the target computer. However, when I recently managed an XP system computer, I encountered a problem where I could not connect normally. Finally, this problem is solved by querying the information. I hope you can solve the problem quickly when you encounter the same problem.

I. Remote Desktop Connection failure

I have just installed an employee computer. The computer operating system is windows XP. After the leaders decide that this computer will be used for data storage in the company, so they need to perform remote management operations in the future. As usual, the Remote Desktop Connection function of the system is enabled. Who knows that when other computers in the network access through the Remote Desktop Connection Program, there is a prompt "Disconnect Remote Desktop Connection, remote computer connection has ended", that is, the connection can be connected but it is interrupted immediately, there is no time to enter the administrator user name and password.

Ii. Solving Problems

Now that you can connect to the computer, it is interrupted immediately. I suspect that the current account is used by default during Remote Desktop login, so I set my computer account and password to be consistent with the remote computer. Who knows the problem persists. It seems that the fault is caused by the Remote Desktop service of the computer. The author sought help online and finally found the problem.

Step 1: Click Start> RUN> enter regedit to open the Registry Editor.

Step 2: Open the registry, find the [HKEY_LOCAL_MACHINESYSTEMControlSet001EnumRootRDPDR key value, right-click the RDPDR on the left, and select "permission ".

Step 3: In the pop-up permission setting window for RDPDR, add the everyone group to the full control permission. If you only want a specific user to remotely manage the computer, add the account to the permission settings window. Remember to grant "full control.

Step 4: copy the following content to a txt file in notepad and save it as a file suffixed with. reg. For example, I save it as 111.reg.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESYSTEMControlSet001EnumRootRDPDR000]

"ClassGUID" = "{4D36E97D-E325-11CE-BFC1-08002BE10318 }"

"Class" = "System"

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

, 00

"Driver" = "{4D36E97D-E325-11CE-BFC1-08002BE10318} 030"

"Mfg" = "(standard system device )"

"Service" = "rdpdr"

"DeviceDesc" = "Terminal Server Device redirection"

"ConfigFlags" = dword: 00000000

"Capabilities" = dword: 00000000

Step 5: double-click the saved Registry File 111.reg. if the prompt "Registry import successful" appears, the operation is correct.

Step 6: Click Start> RUN> enter services. msc to open the Service Management window and find the services named "Remote Desktop Help Session Manager" and "Telnet.

Step 7: Right-click the two service names and select start to enable the Service.

Step 8: After the computer is restarted, we can access the computer through the Remote Desktop Connection Program without any problems. The program automatically enters the step of entering the Administrator account and password.

So far, we have solved the problem of remote desktop program interruption by starting the service, importing the registry, and modifying the registry key value and permissions, we can easily and normally use remote management programs to manipulate computers on the other end of the network.

Summary

This fault is actually caused by the use of the lite version xp ghost or the XP Universal GHOST circulating in the network when the operating system is installed. In these ghosts, the remote desktop program is disabled by default, some necessary permissions for using the registry key value are modified. Although personal users in ordinary families can improve security and prevent illegal users from connecting to computers through remote desktop, it is inconvenient for enterprises. Therefore, the author suggests that network administrators should try to choose XP ghosts that have not been simplified or directly use system CDs to install their computer operating systems in the future, after all, there are more or less problems with GHOST usage.