Re: Admin Account locked out every hour.

Services for sure? Also scheduled tasks?


"Serventek" <Serventek@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:730335D1-8D9B-4197-A469-C2C6DF7E1C82@xxxxxxxxxxxxxxxx
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: Second domain controller does not take over in case the first fail
    ... Recently I did a test shutting down first our primary domain controller, ... which is both GC server and holds all the FSMO roles. ... local service credentials. ... DC1 was running perfectly at ...
    (microsoft.public.windows.server.active_directory)
  • Re: Demoting a DC in W2003
    ... forrest / single domain with three DCs. ... It's only role is being a DC and our primary internal DNS server. ... transfered the FSMO roles from DC1 to DC2 using the MS KB article 324801. ... The local domain controller has attempted to replicate the following object from the following source domain controller. ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain Mess - Problem promoting second server to DC
    ... > I was able to bring up a second domain controller on an old PC ... but DC1 died before I was able ... > the AD that was now running on DC2. ... > I installed DNS on DC2, and configured DC2 to use itself for DNS. ...
    (microsoft.public.windows.server.dns)
  • Re: Domain controller name -rename issue
    ... Because you did not know what your predecessor have done with the DC1 renaming, i would make sure that the correct existing DC2 have all 5 FSMO roles and is GC server and DNS with AD integrated zones only for the correct old named "domain" domain. ... AD users and computers and AD sites and services is cleaned up you can now promote the old DC1 again to domain controller. ...
    (microsoft.public.windows.server.active_directory)
  • 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 ...
    (microsoft.public.windows.server.active_directory)