Re: HELP, I cannot figure this one out.......
- From: "Karl Middleton" <nospam@xxxxxxxxxx>
- Date: Sat, 17 Dec 2005 09:56:35 +1100
If the problem is widespread I would say your time syncing is not working.
Kerberos will throw this error if there is significant enough mismatch in
the time between servers and/or workstations.
Make sure that w32time is running on all the servers and that one of them
has a reliable time source EG: ntp.yourisp.com or one of the stratum 2 time
servers (Google ntp to locate a suitable one). A review of your event logs
should confirm this theory by showing reds in the System log against w32time
on the servers and workstations.
Karl from Oz
"Ryan Pair" <Ryan Pair@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6DED745C-0292-4C1B-A083-B57D7CA5C236@xxxxxxxxxxxxxxxx
> Ok,
> On multiple Servers at different locations i am getting thousands of these
> errors. Has anyone seen this or found a solution to this??
>
> Source Event ID Last Occurrence Total Occurrences
> Security 537 12/15/2005 6:03 PM 9,498 *
> Logon Failure:
> Reason: An error occurred during logon
> User Name: JBarfield
> Domain: xxxxxxxxxxxxxxxxxxxxxxx
> Logon Type: 3
> Logon Process: Kerberos
> Authentication Package: Kerberos
> Workstation Name: -
> Status code: 0xC00002EE
> Substatus code: 0x0
> Caller User Name: -
> Caller Domain: -
> Caller Logon ID: -
> Caller Process ID: -
> Transited Services: -
> Source Network Address: -
> Source Port: -
>
.
- Prev by Date: Re: SBS 2003 Disaster Recovery and/or Hardware Upgrade Same Domain
- Next by Date: Re: Exchange 2003 SP2
- Previous by thread: Re: SBS 2003 Disaster Recovery and/or Hardware Upgrade Same Domain
- Next by thread: Re: managing client computers
- Index(es):
Relevant Pages
|
