Re: Error Code 537
- From: "Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
- Date: Thu, 30 Jun 2005 15:13:03 -0500
Hi Mitch ;-),
Kerberos authentication issues are most often as a result of a time
synchronization problem between the client and server. Check the time and
date on both, do they differ much?
What OS on the workstation in question?
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
"Mitch Garvis, MCSA" <MitchGarvisMCSA@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:9E0EDD65-F7D3-41AB-BE88-054B07BE50F8@xxxxxxxxxxxxxxxx
>I am encountering an issue that has been creating an inordinate number of
> Failed Security Audit events in my SBS (SP1) Security Log.
>
> Logon Failure:
> Reason: An error occurred during logon
> User Name: (username)
> Domain: (domainname)
> 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: -
>
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> --
>
> I have checked the time issue, and I have also added Outlook to the
> Windows
> Firewall exception list in SBS Group Policy. Any other ideas? I await
> your
> genius!
>
> Mitch
> Mitchell D. Garvis, MCSA
> www.e-mitch.com
.
- Follow-Ups:
- Re: Error Code 537
- From: Mitch Garvis, MCSA
- Re: Error Code 537
- References:
- Error Code 537
- From: Mitch Garvis, MCSA
- Error Code 537
- Prev by Date: RE: Remote Access
- Next by Date: Re: Company Web Problem
- Previous by thread: Error Code 537
- Next by thread: Re: Error Code 537
- Index(es):
Relevant Pages
|