Windows Time

[Ross Fisher]

I have a Windows 2000 Server that has been gaining time.
over a 2 week period it may gain 20minutes. The client
has a time senstive application that gts really upset by
this.

Is this likely to be a hardware or software problem? we
have already changed the Bios battery and updated the
Bios to the latest, but still get the same problem.

Also, if we point the server to a time service, ie "net
time /setsntp:192.5.41.209", how often does this sync the
time?

Thanks

 

[George Hester]

I think like once ever 10 minutes but I think you can configure that. Look up Time Service in the Microsoft Knowledge base.

 

[SaltPeter]

I have a Windows 2000 Server that has been gaining time.
over a 2 week period it may gain 20minutes. The client
has a time senstive application that gts really upset by
this.

Is this likely to be a hardware or software problem? we
have already changed the Bios battery and updated the
Bios to the latest, but still get the same problem.

Also, if we point the server to a time service, ie "net
time /setsntp:192.5.41.209", how often does this sync the
time?

Thanks

Its most likely not a hardware problem.

The response depends on whether the server participates in a domain and the
time skew between server and time authority dictates the update periods. If
the server is on a W2K domain, it should be syncing with its PDC emulator.
Search for the wintimeserv.doc whitepaper on google or at Microsoft.

<quote from MS's wintimeserv.doc>
When the local clock offset has been determined, the following algorithm is
used to adjust the time:
· If the local clock time of the client is behind the current time received
from the server, W32Time will change the local clock time immediately.
· If the local clock time of the client is more than three minutes ahead of
the time on the server, W32Time will change the local clock time
immediately.
· If the local clock time of the client is less than three minutes ahead of
the time on the server, W32Time will quarter or halve the clock frequency
for long enough to bring the clocks into sync. If the client is less that 15
seconds ahead, it will halve the frequency; otherwise, it will quarter the
frequency. The amount of time the clock spends running at an unusual
frequency depends on the size of the offset that is being corrected.
<unquote>