Re: Event ID: 537 Kerberos
- From: "Richard Oltmann" <roltmann62@xxxxxxxxxxx>
- Date: Thu, 28 Jul 2005 19:43:49 -0500
try this link and see if any of this is helpful
http://www.eventid.net/display.asp?eventid=537&eventno=194&source=Security&phase=1
Richard
"Evan" <ewgny@xxxxxxxxxxx> wrote in message
news:OaDaHQ9kFHA.2444@xxxxxxxxxxxxxxxxxxxxxxx
> Greetings
>
> I'm getting the following error on
> My windows 2003 member servers when I log on with
> my Domain Admin account
> Domain is a Windows 2000 Domain
> I think this happened after SP1 was installed on the member servers
>
> I did find that the Status code: 0xC000040A
> relates to
> STATUS_NO_S4U_PROT_SUPPORT
>
> However I cannot find much info on this
>
> Any input would be appreciated
>
> Thanks
>
> - Evan
>
>
>
>
>
> Event Type: Failure Audit
> Event Source: Security
> Event Category: Logon/Logoff
> Event ID: 537
> Date: 7/28/2005
> Time: 8:01:46 PM
> User: NT AUTHORITY\SYSTEM
> Computer: SERVER-2
> Description:
> Logon Failure:
> Reason: An error occurred during logon
> User Name:
> Domain:
> Logon Type: 3
> Logon Process: Authz
> Authentication Package: Kerberos
> Workstation Name: SERVER-2
> Status code: 0xC000040A
> Substatus code: 0x0
> Caller User Name: SERVER-2$
> Caller Domain: XYZ
> Caller Logon ID: (0x0,0x3E7)
> Caller Process ID: 1004
> Transited Services: -
> Source Network Address: -
> Source Port: -
>
>
>
>
>
.
- Follow-Ups:
- Re: Event ID: 537 Kerberos
- From: Evan
- Re: Event ID: 537 Kerberos
- References:
- Event ID: 537 Kerberos
- From: Evan
- Event ID: 537 Kerberos
- Prev by Date: Event ID: 537 Kerberos
- Next by Date: Re: Best Practices for File Storage
- Previous by thread: Event ID: 537 Kerberos
- Next by thread: Re: Event ID: 537 Kerberos
- Index(es):
Relevant Pages
|