Help Center/ Elastic Cloud Server/ User Guide (Kuala Lumpur Region)/ FAQs/ Login and Connection/ Remote Login Errors on Windows/ Why Does an ECS Fail to Be Remotely Connected Using RDP and Internal Error Code 4 Is Displayed?
Updated on 2024-04-19 GMT+08:00
View PDF
Share

Why Does an ECS Fail to Be Remotely Connected Using RDP and Internal Error Code 4 Is Displayed?

Symptom

An internal error is displayed when you log in to a Windows ECS and you fail to connect to the ECS remotely. Generally, this problem occurs because the Remote Desktop Services is busy.

Possible Causes

The Remote Desktop Services is busy.

The remote desktop is disconnected after login but is not logged out. To prevent this problem, log out of the ECS if you do not need to remotely connect to it.

Solution

  1. Use VNC provided by the management console to remotely log in to the ECS.
  2. Open the Windows search box, enter services, and select Services.
  3. In the Services window, restart Remote Desktop Services. Ensure that Remote Desktop Services is in the Running status.
    Figure 1 Remote Desktop Services
  4. Remotely connect to the ECS again.

    If the connection still fails, run the cmd command on the local server as the administrator, run the netsh winsock reset command to restore the default network connection configurations, and then retry the remote connection.