Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies. Only from Platform Scholar.
Course Of The Month
1 day, 18 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
AD accounts not getting locked out properly ID 4771
Posted on 2012-12-27
Hello,
I'm receiving many event ID's for 4771 on several domain controllers where I'm getting the below information with many authentication failures but the user accounts are not getting locked out when the default domain policy is set to lockout after 3 unsuccessful attempts. Any thoughts? Thanks
4771,AUDIT FAILURE,Microsoft-Windows-
I'm receiving many event ID's for 4771 on several domain controllers where I'm getting the below information with many authentication failures but the user accounts are not getting locked out when the default domain policy is set to lockout after 3 unsuccessful attempts. Any thoughts? Thanks
4771,AUDIT FAILURE,Microsoft-Windows-
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
4
2
2
8 Comments
Over what time period are these failures occuring?
Are your default settings set to a short grace period?
Are your default settings set to a short grace period?
I'm seeing like 8 failures in a day on this first account I'm looking at. Here is our default domain policy specifically the password piece.
Policy Setting
Enforce password history 5 passwords remembered
Maximum password age 45 days
Minimum password age 1 days
Minimum password length 8 characters
Password must meet complexity requirements Enabled
Store passwords using reversible encryption Disabled
Account Policies/Account Lockout Policyhide
Policy Setting
Account lockout duration 10080 minutes
Account lockout threshold 3 invalid logon attempts
Reset account lockout counter after 4320 minutes
Account Policies/Kerberos Policyhide
Policy Setting
Enforce user logon restrictions Enabled
Maximum lifetime for service ticket 600 minutes
Maximum lifetime for user ticket 10 hours
Maximum lifetime for user ticket renewal 7 days
Maximum tolerance for computer clock synchronization 5 minutes
Policy Setting
Enforce password history 5 passwords remembered
Maximum password age 45 days
Minimum password age 1 days
Minimum password length 8 characters
Password must meet complexity requirements Enabled
Store passwords using reversible encryption Disabled
Account Policies/Account Lockout Policyhide
Policy Setting
Account lockout duration 10080 minutes
Account lockout threshold 3 invalid logon attempts
Reset account lockout counter after 4320 minutes
Account Policies/Kerberos Policyhide
Policy Setting
Enforce user logon restrictions Enabled
Maximum lifetime for service ticket 600 minutes
Maximum lifetime for user ticket 10 hours
Maximum lifetime for user ticket renewal 7 days
Maximum tolerance for computer clock synchronization 5 minutes
What is your Reset Account Lockout Counter After setting?
Go through this as well to make sure all settings are set correctly
http://technet.microsoft.com/en-us/library/cc781491(v=ws.10).aspx
Run gpupdate on client
Run gpresult see if the policy is applying or not to the users
Go through this as well to make sure all settings are set correctly
http://technet.microsoft.com/en-us/library/cc781491(v=ws.10).aspx
Run gpupdate on client
Run gpresult see if the policy is applying or not to the users
Check your 'Reset account Lockout Counter After' setting. This determines how many minutes can elapse after each failed attempt. Your 8 attempts per day may be occuring far enough apart not to trigger the lockout.
http://technet.microsoft.com/en-us/library/cc784599%28v=ws.10%29.aspx
http://technet.microsoft.com/en-us/library/cc784599%28v=ws.10%29.aspx
I've requested that this question be closed as follows:
Accepted answer: 0 points for jacksonwsa's comment #a38757651
for the following reason:
This was never resolved
Accepted answer: 0 points for jacksonwsa's comment #a38757651
for the following reason:
This was never resolved
Featured Post
We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Suggested Solutions
It’s been over a month into 2017, and there is already a sophisticated Gmail phishing email making it rounds. New techniques and tactics, have given hackers a way to authentically impersonate your contacts.How it Works
The attack works by targeti…
- Phishing
- The Email Laundry
- Email Servers
- Cybersecurity
- Email Protocols
- Network Security, Security
This article outlines the process to identify and resolve account lockout in an Active Directory environment.
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
- Windows 10
- Microsoft Legacy OS
- Windows 8
- Windows OS
- Windows 7
- Windows Vista, *Windows Explorer, Windows XP, *Internet Explorer (IE), Windows 2000
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
Suggested Courses
Course of the Month1 day, 18 hours left to enroll
710 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.