Step 9-13| There is no clear error message when the remote connection fails

Step 9: Check CPU load, bandwidth, and memory usage

When unable to remotely connect to a Windows instance normally, it may be due to CPU load, insufficient bandwidth, or insufficient memory.

1. Select the corresponding operation based on whether there is an excessive CPU load.

There is no high CPU load situation, please continue with step 2 to continue troubleshooting.

If the CPU load is too high, please refer to this step to solve the problem.

1) When checking for high CPU load, log in to the instance through the terminal on the instance details page to check if the Windows Update operation is being executed in the background. If there is a Windows Update operation, high CPU load is a normal result. Please continue to wait for the execution to complete.

2) If the application has a large amount of disk access, network access behavior, and high computing requirements, high CPU load is a normal result. We suggest that you upgrade the instance specifications to address resource bottlenecks.

2. Check if there is an issue of insufficient public network bandwidth.

The inability to connect remotely may be caused by insufficient public network bandwidth. The specific troubleshooting method is as follows.

1) Log in to the ECS management console.

2) At the top left corner of the menu bar, select the region.

3) On the instance list page, click the corresponding instance ID, and in the basic information area, view the current bandwidth usage.

If the server bandwidth is 0 Mbps, it indicates that the public network bandwidth was not purchased when purchasing the instance. You can solve this problem by upgrading the bandwidth. For specific operations, please refer to Modifying Public Network Bandwidth.

3. Check for insufficient memory issues.

After connecting to a Windows instance remotely, it is not possible to display the desktop normally and exit directly, and there is no error message prompt. This situation may be caused by insufficient server memory, and it is necessary to check the memory usage of the server. The specific operation is as follows.

1) Log in to a Windows instance using VNC mode.

2) Select Start>Management Tools>Event Viewer to check whether there is warning log information of insufficient memory resources.

Step 10: Check the security policy settings of the system

You can check if there are relevant security policies on the Windows server that prevent remote desktop connections.

1. Log in to a Windows instance using VNC mode.

2. Select Start>Control Panel>Administrative Tools, double-click Local Security Policy.

3. In the Local Security Policy interface, click IP Security Policy, and on the local computer, select the corresponding action based on whether there is a relevant security policy.

There is a relevant security policy, delete or re edit it

Delete Security Policy: Right click on the relevant policy, select Delete (D), and in the pop-up dialog box, click Yes.

Double click to open the security policy for this IP, reconfigure to allow remote desktop connections, and then use remote desktop connections again.

There are no relevant security policies. Follow step ten: Check the system's security policy settings to continue troubleshooting.

Step 11: Check the antivirus software

The inability to connect to ECS instances using remote desktop may be due to third-party antivirus software settings, which can be resolved through the following methods. Here are two solutions to remote access failures caused by security dog configuration.

If the antivirus software is running in the background, you can log in to the instance through VNC to upgrade the antivirus software to the latest version or directly delete it.

Please use commercial antivirus software or use Microsoft Safety Scanner's free security tool to scan for antivirus in secure mode.

Step 12: Windows Registry Configuration Exception

Abnormal configuration of the Windows registry may cause RDP connections to be blocked. You can refer to the following steps to fix it.

1. Connect ECS instances using VNC.

2. Enter regedit in the Run box, click OK, and open the Registry Editor.

3. In the registry editor, modify the parameter configuration separately.

Step 13: Windows RDP self signed certificate expires

The expiration of the RDP self signed certificate may result in the inability to log in remotely. You can refer to the following steps to fix it.

1. Log in to a Windows instance using VNC mode.

2. Run Windows PowerShell as an administrator.

In the Windows PowerShell dialog box, execute the command.