Link to home
Start Free TrialLog in
Avatar of SecGeek
SecGeekFlag for United States of America

asked on

Accounts getting disbled in active directory.

Here is my situation.  Today dozens of accounts were locked by Active Directory disabling all the users PKI common access cards as a by product.

Here what I know:

Dozens of user accounts are listed as logging on to Retina Scanner appliance (a vulnerability scanner).  The loggins are passed on to the server, verifed and disabled via the same local DC.  This occurred over a period of four hours or so.  We checked the logs for jobs on the Retina server and so far can't find anything wonky in the event logs figuring the local security logs would not be useful since they are AD logons and will be on the DC.
Being that all of these accounts attempted logons to a particular subnet which is not it's normal AOR (Area of Responsibility) is strange.
WE do have logs from DC showing the attempts and subsequent locking of the accounts that targeted the particular serve but no idea why they would all to do in hat looks to be an automated fashion

Again, but any help would be appreciated.
We cannot match up any running scan jobs at the time of login attempts.
Besides why would a vulnerability scanner be the target (not the initiator) of dozens of unsuccessful logons from the same subnet?
Finally the logon attempts causng the lock outs where definitely automated as they where hapening less that a second appart.

I have no idea so far where else to look and I'm supposed to tell the boss what going on by the end of tommorow.  I'm not asking someone to do my work for me but maybe suggest other things to consider.
The more paranoid of us immediately suggested some grand AD aware piece of malware but I would rather start at something more mundane.
My only hunch is that somehow the Retina server will be culprit,not the target as the logs show because it's job is to rapidly scan swath of IP's, but again no apparent jobs where running at the time....

Sorry fore the long description but wanted you to know I'm not looking for free hand outs :-)
Avatar of johnb6767
johnb6767
Flag of United States of America image


In the security logs, you should be able to find the source of the lockout on the server, and in the client, you should see a Logon Type code
Logon Type Codes Revealed
http://www.windowsecurity.com/articles/Logon-Types.html
Avatar of Arisglobal
Arisglobal

have you installed antivirus , isit upto date with the virus definitions ?

do a full scan on the server
Hi,

The frequent account lockout issue in a domain may occur due the downtab/conflicker worm activity on your network.Install the following patches on the computers.

1. http://support.microsoft.com/kb/958644
2. http://support.microsoft.com/kb/890830(Microsot Malicious Software Removal Tool)

After intsalling these patches restart the computer and run a full scan with Microsot Malicious Software Removal Tool using followng command

c:\windows\system32\mrt.exe /F:Y

Do the above steps on the suspected computers, you can find these computers from the account lockout logs in the security log.
ASKER CERTIFIED SOLUTION
Avatar of btan
btan

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of SecGeek

ASKER

Thank you every one for your help.  Breadtan you were very close to the what we determined to be the solution.  We always suspected that the Retina server was causing the lockouts.  The rub was that when we looked at the AD DC logs and the Retina scanner Job times.  They didn't match up.  So it messed me up for a bit.
 
Essentially, I was an idiot. My organization does not adhere to UTC (or any NTP) specifically.  One log was in UTC and the other was in the Retina scanners time zone. So I concluded that it might not be the scans after all and started looking elsewhere.

Once, someone pointed out that "duh"  I had a time zone issue and that the scans WERE running when the lock out began, I looked at the scan configurations and sure enough the password strength checks were on!

They had always been erroneously set as on but did not come to light until a GPO change changed account lock out time to permanent which triggered a ton of complaints.

It's fixed now.

Thanks again.
Avatar of SecGeek

ASKER

Very good advice. We came to the solution slightly differently but would have found it through breadtan's solution.