ESXI system password login failed
1. Background
Since the esxi version was upgraded to 6.5+, I often encountered "the user name or password is incorrect, and the error of logging in cannot be completed". This problem has plagued IT colleagues for a long time. Someone once posted that there is a bug in esxi6.5, and it is enough to upgrade to U3 or later. And this problem is sometimes very strange:
- The web interface cannot be logged in, but the console console connected to the monitor can log in normally
- The web interface cannot be logged in, but it has been added to VCSA/VcenterVsphere but can be managed normally
Looking at the Internet and the technical community, many people will restart the business, reset the system or crack the password in linux pe, and reset the password.
Just happened to encounter this problem again today, and recorded it.
2. Cause of failure
This phenomenon:
The web interface cannot log in to the system, prompting that the password is incorrect, but VCSA can manage normally. Log in to VCSA, check the log and find:
It turned out that due to the large number of real logins on the web interface, the user was temporarily locked. The main reason is that esxi6 began to introduce the root account lock function. When the number of login failures reaches a certain amount (the default is 5 times), there will be a 900-second account lock time. This time is cumulative. Either modify the authentication policy, or wait 900s and enter again, but it will be sad to make an error again after 900s.
Problems encountered before:
The problem encountered before is similar to this time, and the reason is the same. After logging in to Vcenter Vsphere, I found that I failed more than 1000 times. I thought I was attacked. Finally, I found out that the IP of ESXI was the IP of other businesses that went offline before. , but because the current ip is ESXI, the login fails every time.
Possible situations:
- esxi ip address conflict caused
- esxi password forgotten, too many retries
- esxi is under scan attack
3. Solutions
Modify the security policy and reset the number of wrong passwords:
Change the value of Security.AccountLockFailures to 0 in the advanced settings
No one has changed the password. This phenomenon occurs because esxi6 began to introduce the root account lock function. When the number of login failures reaches a certain amount (the default is 5 times), there is a 900-second account lock time. This time is cumulative. Change the value of Security.AccountLockFailures to 0 in the advanced settings