Solution to the error "For security reasons, this user account has been locked due to too many login attempts or password change attempts" when connecting to a Windows instance via remote desktop


1. Problem description


When using Remote Desktop to connect to an ECS instance on a Windows system, an error message " For security reasons, this user account has been locked due to too many login attempts or password change attempts " is prompted. The specific error message is as shown in the figure below.


Insert image description here


2. Cause of the problem


The user lock policy is configured in the ECS instance system group policy of the Windows system. If you enter an incorrect password too many times when logging in, the account will be locked, making it impossible to log in to the remote desktop.


3. Solution


You can modify the Windows instance Group Policy account lockout threshold to 0 to solve this problem. This article uses the Windows Server 2019 operating system as an example. The steps for other operating systems are similar.

  1. Connect to Windows instance via VNC.

When you cannot use Workbench and third-party remote connection tools (such as PuTTY, Xshell, SecureCRT, etc.) to connect to the instance, you can log in to the instance through VNC remote connection.

For specific methods, different service providers provide different consoles, so please check it yourself.


  1. Enter the command in the search dialog box in the lower left corner of the system gpedit.msc, and then click OK to enter the Local Group Policy Editor page.

Insert image description here


3. In the Local Group Policy Editor page, select Computer Configuration > Windows Settings > Security Settings > Account Policies > Account Lockout Policy .

Insert image description here


4. On the Account Lockout Policy page, double-click the Account Lockout Threshold to enter the Account Lockout Threshold Properties window.


5. In the Account Lock Threshold Properties window, change the account non-lock threshold to 0 and click OK .

Insert image description here


6. Reconnect the remote desktop to the Windows instance.


Guess you like

Origin blog.csdn.net/lizhong2008/article/details/135185523