Security

Ask something
Discussion Locked

Error occurred during logon Event ID 537

0 helpful
8 replies

by wkpowers

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

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 ID: -
Caller Process ID: -
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?

8 replies

by amberhaze

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.

by amberhaze

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 blow up every time.

by lowlands

AmberHaze is correct. Status code 0xC0000133 means STATUS_TIME_DIFFERENCE_AT_DC.

So verify the time between the fileserver and you DC.

by wkpowers

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.

by pcofranc

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.

by rhid

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

This discussion is closed to new replies.