Re: Admin Account locked out every hour.

The dcdiag may provide the info needed to determine the issue. You should
run as previously described.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
http://www.pbbergs.com/

This posting is provided "AS IS" with no warranties, and confers no rights.


"Serventek" <Serventek@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:890A13A6-BCB6-466C-9707-E685CC4C51AB@xxxxxxxxxxxxxxxx
I rebooted several times since the issue started occuring. All the errors
that I posted really are just saying that someone is trying to log in
using
the administrator account and basically using the wrong password. I feel
that if I can find out what is running everyhour then I can determine the
job
or process that is responsible for using the account and old password.
BTW -
the logs show that this authentication (every hour) was happening
successfuly
before the password changed.
--
Thanks -LRG


"Paul Bergson" wrote:

I am not certain on this but it appears that Kerberos is having trouble
authenticating. I would simply attempt to reboot the dc and see if that
helps (Although you have probably already done that).

You could look at the link below on Kerberos troubleshooting:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerberr.mspx

Also you should consider running diagnostics against your dc to see if
there
are any underlying issues.

Go to http://www.pbbergs.com

Select downloads and select the DCDiag and NetDiag Gui this will provide
a
front end GUI for diagnostics for your network.

--
Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA


"Serventek" wrote:

We changed the administrator account's password and since then we have
been
seeing it locked out every hour. I have the lockout tools from
microsoft.
The lockout originates from the domain controller DC1. Every hour I
get this
error in the event log of DC1.


Event Type: Failure Audit
Event Source: Security
Event Category: Account Logon
Event ID: 675
Date: 2/17/2006
Time: 5:00:14 PM
User: NT AUTHORITY\SYSTEM
Computer: DC1
Description:
Pre-authentication failed:
User Name: Administrator
User ID: companyname\Administrator
Service Name: krbtgt/companyname
Pre-Authentication Type: 0x2
Failure Code: 0x18
Client Address: 127.0.0.1

I have triple checked the services and all processes running on the
server.
None seem to using the Administrator account. Eventcomb shows the
following
errors every hour:

675,AUDIT FAILURE,Security,Mon Feb 17 17:00:12 2006,NT
AUTHORITY\SYSTEM,Pre-authentication failed: User Name:
Administrator
User ID: %{S-1-5-21-1118139714-1942908946-495535119-5467} Service
Name:
krbtgt/companyname Pre-Authentication Type: 0x2 Failure Code:
0x18
Client Address: 127.0.0.1


I turned on Netlogon logging which logs the following every hour:

02/17 17:00:52 [LOGON] companyname: SamLogon: Network logon of
companyname\administrator from DC1 Entered
02/17 17:00:52 [LOGON] companyname: SamLogon: Network logon of
companyname\administrator from DC1 Returns 0xC0000234

Kerberos logs the following at around the time:


Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 3
Date: 2/17/2006
Time: 5:00:16 PM
User: N/A
Computer: DC1
Description:
A Kerberos Error Message was received:
on logon session companyname.COM\dc1$
Client Time:
Server Time: 1:3:42.0000 2/20/2006 Z
Error Code: 0x18 KDC_ERR_PREAUTH_FAILED
Extended Error:
Client Realm:
Client Name:
Server Realm: companyname
Server Name: krbtgt/companyname
Target Name: krbtgt/companyname@companyname
Error Text:
File: e
Line: 6bc
Error Data is in record data.

I find it interesting that the account lockout events above occur every
hour
all day and that the source address is 127.0.0.1, which means that the
source
is itself (domain controller, DC1). I have checked schedule jobs in
the
controll panel and through the AT command as well. Nothing is schedule
via
these.

Thanks -LRG


.

Relevant Pages

  • Re: Admin Account locked out every hour.
    ... Yes I checked all the services and scheduled tasks. ... The lockout originates from the domain controller DC1. ... Event Source: Security ... Event Category: Account Logon ...
    (microsoft.public.windows.server.active_directory)
  • Re: Domain controller Stop functioning
    ... > master and it did not hangs, but DC2 start acting like DC1, that hang now. ... > Event Source: NETLOGON ... > Event Type: Warning ... > Replication Service while polling the Domain Controller DC1.root.local for ...
    (microsoft.public.windows.server.active_directory)
  • Re: Admin Account locked out every hour.
    ... out the account to see what would happen. ... Using the NLPARSE tool (from the Account Lockout and Management Tools - ... the administrator account and basically using the wrong password. ... The lockout originates from the domain controller DC1. ...
    (microsoft.public.windows.server.active_directory)
  • ###### C Drive not visible
    ... The DC1 is still operational. ... A user account in one or more Group policy objects (GPOs) could not be ... 2.Identify the GPOs that contain the unresolvable account name: ...
    (microsoft.public.win2000.file_system)
  • RE: Admin Account locked out every hour.
    ... The lockout originates from the domain controller DC1. ... None seem to using the Administrator account. ... Client Address: 127.0.0.1 ... I turned on Netlogon logging which logs the following every hour: ...
    (microsoft.public.windows.server.active_directory)