Invalid clock changes

[Larry Clawson]

Since replacing our NT4 LAN server w/W2K server, our
server and W2K clients clocks get changed by -15 (for some
weeks) and since then by -16 minutes. Once changed like
this, the clocks remain off by that amount. The server is
changed after a longer time -- many hours, whereas the
clients get changed after just a few hours. These et's
are from when the clock is manually set to the correct
time. An XP client gets changed by an hour, but the NT4's
do not have clock problems.

 

[Jason Hall [MSFT]]

--------------------

Content-Class: urn:content-classes:message
From: "Larry Clawson" <[email protected]>
Sender: "Larry Clawson" <[email protected]>
Subject: Invalid clock changes
Date: Wed, 2 Jun 2004 13:50:19 -0700

Since replacing our NT4 LAN server w/W2K server, our
server and W2K clients clocks get changed by -15 (for some
weeks) and since then by -16 minutes. Once changed like
this, the clocks remain off by that amount. The server is
changed after a longer time -- many hours, whereas the
clients get changed after just a few hours. These et's
are from when the clock is manually set to the correct
time. An XP client gets changed by an hour, but the NT4's
do not have clock problems.

--------------------

Check out these articles to get your network time synchronized...
Q216734: How to Configure an Authoritative Time Server in Windows 2000
Q314054: How to Configure an Authoritative Time Server in Windows XP


--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.