Windows Forum

Ask something
Discussion Locked

Event ID Error 64

0 helpful
5 replies

by ldregely

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

Can someone help me solve this error?
Event Category: None
Event ID: 64
Date: 5/17/2001
Time: 4:28:32 AM
User: N/A
Computer: ENGRLABSRV
Description:
Because of repeated network problems, the time service has not been able to find a domaincontroller to synchronize with for a long time. To reduce network traffic, the time service will wait 960 minutes before trying again. No synchronization will take place during this interval, even if network connectivity is restored. Accumulated time errors may cause certain network operations to fail. To tell the time service that network connectivity has been restored and that it should resynchronize, execute "w32tm /s" from the command line.
Data:
0000: 00 00 00 00 ....
Thank you.

5 replies

by beermonster

I cant say it any better than the technet article - Q258059
(go to www.microsoft.com/technet and search on that number if you don't have a copy)
The reason time is such an issue in win2k is that the Kerberos security protocol timestamps the packets that pass between machines as they communicate. any packet more than (by default) 5 minutes old is discarded - this time period is known as the 'skew'. this limits the time an attacker has to intercept your packet, and tamper with it, before passing it on to you.

by beermonster

I cant say it any better than the technet article - Q258059
(go to www.microsoft.com/technet and search on that number if you don't have a copy)
The reason time is such an issue in win2k is that the Kerberos security protocol timestamps the packets that pass between machines as they communicate. any packet more than (by default) 5 minutes old is discarded - this time period is known as the 'skew'. this limits the time an attacker has to intercept your packet, and tamper with it, before passing it on to you.

This discussion is closed to new replies.