Shulou(Shulou.com)06/02 Report--

Editor to share with you how to solve the problem of being unable to connect to Windows instances, I believe most people do not know much about it, so share this article for your reference. I hope you will learn a lot after reading this article. Let's learn about it together.

Unable to connect to Windows instance

The following figure shows the cause classification and occurrence probability of not being able to connect to ECS instances. If you are unable to connect to the instance, it is recommended to troubleshoot according to the following reasons.

First try to connect remotely

Regardless of the reason why the instance cannot be connected remotely, try to connect with the remote connection feature provided by Aliyun first, and then troubleshoot by reason.

Log in to the CVM management console.

Locate the instance that needs to be connected, and in the instance Action column that needs to connect, click remote Connect.

Connect the management terminal. To connect for the first time, you need to copy the password first.

After entering the password, connect to the instance.

If you forget your password, click if you forget your password, click change the password of the administrative terminal, and set a new password. An instance optimized by Icano, which takes effect immediately after the password is changed, without the need to restart

Unable to connect to ECS instance troubleshooting ideas

Please check one by one according to the following reasons:

Client local network exception [probability: 3%]

Reset the instance password and did not restart the instance [occurrence probability: 7%]

Abnormal firewall configuration (Windows 2008 / 2008 / 2012) [probability of occurrence: 10%]

Security group public network rules [occurrence probability: 8%]

Remote access port configuration exception [probability: 10%]

CPU load is too high [occurrence probability: 9%]

1. Client local network exception [probability: 3%]

Failure phenomenon: the user cannot log on to the external network.

Possible reason: the network card driver is not turned on or there is a problem with the network card configuration.

Solution: check the network card driver and reinstall it.

two。 Reset the instance password and did not restart the instance [occurrence probability: 7%]

Failure phenomenon: there is a record of password modification of the instance, but there is no record of restarting the instance.

Possible reason: you changed the password of the instance, but did not restart the ECS instance.

Solution:

Log in to the CVM management console.

Click the instance in the left navigation bar.

Click the region at the top of the page.

Select the desired instance. Click restart.

In the pop-up prompt box, select restart and click OK.

3. Abnormal firewall configuration (Windows 2008 / 2008 / 2012) [probability of occurrence: 10%]

Prerequisite: you can do this troubleshooting only if you are authorized to turn off the firewall.

Failure phenomenon: unable to connect remotely, the connection is restored after closing the firewall.

Solution: adjust the firewall configuration policy. For more information, please see the firewall settings for ECS Windows remote connections.

After completing the operation, please make a remote connection again.

4. Security group public network rules [occurrence probability: 8%]

Failure phenomenon: ECS server can not ping, troubleshooting firewall, network card IP configuration is correct, still can not ping after rolling back the system.

Possible reason: the default public network rule of ECS instance security group has been deleted.

Solution: reconfigure the public network rules of the security group of the ECS instance. For more information, please see the deletion of the default public network rule of the security group of the ECS instance, which makes it impossible to communicate with ping.

5. CPU overload [occurrence probability: 9%]

Failure: the CPU load is too high to allow the system to connect remotely.

Solution:

If the antivirus software is executed in the background, please upgrade the antivirus software to the latest version or delete it directly.

Please use the commercial version of the antivirus software, or use Microsoft's free security tool Microsoft Safety Scanner to scan for antivirus in safe mode. The link is as follows: https://www.microsoft.com/security/scanner/zh-cn/default.aspx.

Check whether the backend is performing a Windows Update operation when the CPU is soaring.

Run Windows Update to install the latest Microsoft security patches.

If the application has a large amount of disk access / network access behavior / high computing requirements, high CPU is the normal result. You can try to upgrade the instance specifications to solve the resource bottleneck problem.

For more information, see: ECS Windows Server CPU processing with High occupancy.

Finally, try to restart the instance

Restart will cause the instance to stop working, thus interrupting the business. Please proceed with caution.

Note: before restarting the instance, you need to create a snapshot of the instance for data backup or image creation. For more information on how to create a snapshot, see: create a snapshot.

Restart the instance on the console. After restarting the instance, try connecting to the instance again.

The above is all about how to solve the problem of not being able to connect to the Windows instance. Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.