Help Center > > FAQs> Login and Connection> Remote Logins> What Should I Do If I Cannot Log In to My Windows ECS?

What Should I Do If I Cannot Log In to My Windows ECS?

Updated at: May 06, 2020 GMT+08:00

Symptom

An ECS cannot be logged in due to some reasons, for example, the network malfunctions, the local port for accessing the remote desktop is denied on the firewall, or the CPU is overloaded on the ECS.

If this issue occurs, follow the instructions provided in Attempting Login Using VNC on the Management Console. Then, locate the login fault based on Fault Locating.

Attempting Login Using VNC on the Management Console

If the remote login fails, check whether you can log in to the ECS using VNC on the management console.

Click here to learn the preparations for logging in to an ECS.

  1. Log in to the management console.
  2. Under Computing, click Elastic Cloud Server.
  3. In the Operation column of the target ECS, click Remote Login.
    Figure 1 Remote Login
  4. (Optional) When the system displays "Press CTRL+ALT+DELETE to log on", click Ctrl+Alt+Del in the upper part of the remote login page to log in to the ECS.
    Figure 2 Ctrl+Alt+Del

If the login using VNC fails after the preceding operations are performed, record your resources and the time when the fault occurred. Then, click Service Tickets in the upper right corner of the management console, choose Create Service Ticket, and submit a ticket for technical support.

Checking Whether the Network Is Functional

Check whether the EIP bound to the ECS can be pinged.

If the EIP cannot be pinged, resolve this issue by following the instructions provided in Why Cannot an EIP Be Pinged?

After performing the preceding operations, try to remotely log in to the ECS again.

Checking Whether the Firewall Is Correctly Configured

Ensure that the remote access port on the local end is allowed on the firewall. The default port is TCP 3389.

If the port configured in the inbound rule of the firewall is different from that configured on the remote server, the remote login fails. In such an event, add the port configured on the remote server in the inbound rule of the firewall.

The default port is 3389. If you use another port, add that port in the inbound rule of the firewall.

After performing the preceding operations, try to remotely log in to the ECS again.

Checking Whether the Remote Access Port Is Correctly Configured

  1. Check whether port 3389 on the ECS is accessible.

    Ensure that port 3389 has been added in the inbound rule.

  2. Check whether the remote access port on the ECS has been changed.
    1. Choose Start > Run, enter cmd, and press Enter. In the CLI, enter regedit to open Registry Editor.
    2. In HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP Tcp\PortNumber, check whether the port is the default one, port 3389. If not, change the port to the configured one for remote logins.

  3. Check whether the number of connections to the ECS is limited.

    Check the internal remote desktop configuration of the ECS.

    1. Choose Start > Run, enter cmd, and press Enter. In the CLI, enter gpedit.msc to open Local Group Policy Editor.
    2. Choose Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections. Then, in the Limit number of connections dialog box, check whether the number is limited.

      If Limit number of connections is set to Enabled, a remote connection to the Windows ECS may fail when the number of connections exceeds the limit. In such an event, disable Limit number of connections or set a larger limit for connections.

After performing the preceding operations, try to remotely log in to the ECS again.

Checking Whether the CPU Is Overloaded

If the login failure is caused by high CPU usage, perform the following operations to reduce the CPU usage:
  • Stop certain processes that are not used temporarily and try again.
  • Verify that the Windows Update process is not running on the backend.
  • Restart the ECS.
  • Reinstall the ECS OS. Back up important data before the reinstallation.
  • If the ECS OS cannot be reinstalled due to important data, replace the disk attached to the ECS. To do so, back up data on the original disk, detach the disk from the ECS, attach the new disk to the ECS, and copy data to the new disk.

After performing the preceding operations, try to remotely log in to the ECS again.

Checking Whether an Error Occurs During a Remote Login

If an error message is displayed during a remote login, check the operation guide based on the error information.

If the error cannot be handled, record the message and the time when the error occurred. Then, click Service Tickets in the upper right corner of the management console, choose Create Service Ticket, and submit a ticket for technical support.

After performing the preceding operations, try to remotely log in to the ECS again.

If the fault persists after the preceding operations are performed, record your resources and the time when the fault occurred. Then, click Service Tickets in the upper right corner of the management console, choose Create Service Ticket, and submit a ticket for technical support.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel