Topic: PC Time Service errors

[Des Dougan]

I'm seeing this message in my Win2K Event Log:

Event Type:   Warning
Event Source:   w32time
Event Category:   None
Event ID:   64
Date:      28/3/2002
Time:      10:50
User:      N/A
Computer:   P133
Description:
Because of repeated network problems, the time service has not been able to find a domain controller 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: e5 03 00 00               å...    


Has anyone else experienced this? What's causing it?

Des Dougan

[Dub Dublin]

I haven't experienced it because I don't run W2K here , but in general, W2K is quite paranoid about maintaining time sync for both security and data integrity reasons.

As a good starting place, check to make sure that either 1) your e-smith box is a lower-stratum time server (this should be the default, anyway, as far as I'm concerned), or 2) that NTP (port 123) is allowed to pass through the gateway and any other firewall in the path.

My guess is that either will fix this, although the first is preferable, as it makes the SME box itself a good master clock for the rest of your network, and you'll know its clock is always right, too.