• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 402
  • Last Modified:

ad account locking

we have a couple of users accounts locking automatically, we think caused by one of our 3rd party software applications.
The issue is that the account is showing locked on our PDC, but the other 3x DCs are not showing this,.

3 Solutions
This seems like an issue with replication not occurring as expected, so the account state is not yet replicated out across the AD.  

Here is some valuable reading:

Do you know what application it is that is causing the failed logins ?
Jim P.Commented:
Pick one of the DCs to make the "PDC". (Yes, know they longer exist.) Set that DC up  to be the authoritative time server from the internet. Then get the other DCs to set their time from the PDC. And it helps if you can push that to all the clients. Or at least use the local DC t set their time.

At one point we had a DC at our DR site. It was running 15 minutes ahead of our PDC at the main site. So it kept bringing back the server that we were trying to replace. Once we fixed the time on the remote DC the issue went away.
CHI-LTDAuthor Commented:
all the clocks/time is okay.

we think its our mimecast app (which uses LDAP) to authenticate with them.  i cant see how this can be locking our local AD account), but sure this is the problem..
Leon FesterSenior Solutions ArchitectCommented:
Download the Account Lockout and Management tools from Microsoft

See some of the features below:
ALTools.exe includes:

AcctInfo.dll. Helps isolate and troubleshoot account lockouts and to change a user's password on a domain controller in that user's site. It works by adding new property pages to user objects in the Active Directory Users and Computers Microsoft Management Console (MMC).

ALockout.dll. On the client computer, helps determine a process or application that is sending wrong credentials.

Caution: Do not use this tool on servers that host network applications or services. Also, you should not use ALockout.dll on Exchange servers, because it may prevent the Exchange store from starting.
ALoInfo.exe. Displays all user account names and the age of their passwords.

EnableKerbLog.vbs. Used as a startup script, allows Kerberos to log on to all your clients that run Windows 2000 and later.

EventCombMT.exe. Gathers specific events from event logs of several different machines to one central location.

LockoutStatus.exe. Determines all the domain controllers that are involved in a lockout of a user in order to assist in gathering the logs. LockoutStatus.exe uses the NLParse.exe tool to parse Netlogon logs for specific Netlogon return status codes. It directs the output to a comma-separated value (.csv) file that you can sort further, if needed.

NLParse.exe. Used to extract and display desired entries from the Netlogon log files.

Accounts that are locked on one DC and not the other could indicate replication issues or high replication times,
Either way, you can run an AD health check by running "dcdiag /e /v /f:dcdiag.txt".

Post the logfile if you need help understanding anything there
CHI-LTDAuthor Commented:
combination of the ip address being blocked and an issue with certificates at the 3rd party end.  Still find it strange that our internal account is/was being locked when the 3rd party software was accessing the 3rd party cloud/website...
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now