Re: 30k plus Event 537's a Day

Hi Jose,
We have this same problem on Three seperate Domain servers. We have yet to
find a solution to this problem. I am sure that it is linked to a system
update, but which one?!?

"Jose Canedo" <JoseCanedo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D35BC525-BA48-4EC8-9483-6A58CE05DB85@xxxxxxxxxxxxxxxx
> I've looked for a solution on here but the solutions given (time
> syncronization and removing and adding the user/computer) haven't worked
> for
> us.
>
> I'm getting the following error for two users:
>
> Event Type: Failure Audit
> Event Source: Security
> Event Category: Logon/Logoff
> Event ID: 537
> Date: 11/18/2005
> Time: 8:19:52 AM
> User: NT AUTHORITY\SYSTEM
> Computer: SBSERVER
> Description:
> Logon Failure:
> Reason: An error occurred during logon
> User Name: scanedo
> Domain: MYBIZ
> 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: -
>
> the weird thing is i also receive the following succesful report:
> Event Type: Success Audit
> Event Source: Security
> Event Category: Logon/Logoff
> Event ID: 538
> Date: 11/18/2005
> Time: 8:19:51 AM
> User: INTSUPINC\scanedo
> Computer: SBSERVER
> Description:
> User Logoff:
> User Name: scanedo
> Domain: MYBIZ
> Logon ID: (0x0,0x2C2E3D67)
> Logon Type: 3
>
> How is it that Logon Type 3 can be succesful 1 second and fail the next?
>
> thanks for the help! it's not causing any problems with the system but
> i'd
> like the system to run nice and tidy and not see the glaring FAILURE every
> day on the reports.


.

Loading