General discussion

Locked

Error occurred during logon Event ID 537

By wkpowers ·
Logon Failure:
Reason: An error occurred during logon
User Name: CPSBACKUP$
Domain: CPS.LOCAL
Logon Type: 3
Logon Process: Kerberos
Authentication Package: Kerberos
Workstation Name: -
Status code: 0xC0000133
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon I -
Caller Process I -
Transited Services: -
Source Network Address: 192.168.0.70
Source Port: 0
I log between 4 and 15 of these errors a day. the address is from a network file server. i'm running SBS 2003. anyone know how to fix this?

This conversation is currently closed to new comments.

8 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by AmberHaze In reply to Error occurred during log ...

Not quite enough information, but here are a couple of things to check out...

Are all machines synchronized to the same time source? A machine who's time is off can cuase this status code.

Also, what backup system are you using? I am suspecting something related to this.

Collapse -

by AmberHaze In reply to

don't forget to double check the dates. I have seen the time be "close" but the date be of by several years, and that will cause a **** up every time.

Collapse -

by lowlands In reply to Error occurred during log ...

AmberHaze is correct. Status code 0xC0000133 means STATUS_TIME_DIFFERENCE_AT_DC.

So verify the time between the fileserver and you DC.

Collapse -

by lowlands In reply to

5 minutes it all it takes for Kerberos

Collapse -

by wkpowers In reply to Error occurred during log ...

the time was only 5 min off...could that be causeing the problem. i'm just using NTbackup. the network file server is running windows embedded and the DC is running SBS 2003.

Collapse -

by wkpowers In reply to Error occurred during log ...

Point value changed by question poster.

Collapse -

Kerbos time issue 2008 2003 server mixed domain

by pcofranc In reply to Error occurred during log ...

I have the exact same errors in the logs and AD is acting wacky. I also have a network latency issue. Any help would be appreciated. This all started after adding new vmware vm's to the domain.

Collapse -

My solution

by rhid In reply to Kerbos time issue 2008 20 ...

I had the same problem. I solved it by manually adding the time server on the command line of the new DC.

C:\Users\Administrator>net time /setsntp:ntp1.cs.wisc.edu

Back to Security Forum
8 total posts (Page 1 of 1)  

Related Discussions

Related Forums