User account locked out windows server 2008 r2

Details required :. Cancel Submit. Bill Smithers Volunteer Moderator. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. This is often a persistent network drive mapping using an old password from another user's workstation perhaps. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Learn more. User account being frequently locked out Ask Question. Asked 9 years, 1 month ago. Active 3 years, 10 months ago.

Viewed 19k times. This just started last week. Improve this question. Richard West Richard West 2, 12 12 gold badges 41 41 silver badges 48 48 bronze badges. Consider the following scenarios. Scenario 1. You use a smart card to log on to the cached locked-out account. The logon fails, and you receive the following error message:. The system could not log you on. Your account has been disabled. Please see your system administrator. You use your username and password to log on to the cached locked-out account.

This causes the cached account to be reported as disabled on the computer. The related cached credentials are then deleted.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. I can now access the shares on the workgroup server without issue and without getting prompted for credentials. If I change the password on the workgroup server to not match the domain accounts password, I immediately get locked out when I access a share.

After searching around, I came across an article similar to this which pointed me at the Net Use command. This listed all established connections to a server. By this time, in testing, I had deleted the local account that matched my domain account for Username, and created a new local account with a different username. So, I need to test if this "solution" works in when the username matches between domain and workgroup. The issue now seems to be how Windows 7 keeps alive network connections vs.

I have also reproduced this issue going to a plain Windows server, so its definitely something new to R2. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Is there a setting in the Local Policy that changes this behavior? Popular Topics in Windows Server. Spiceworks Help Desk. The help desk software for IT.