Timeserver Update Page for ClockWatch Users
Some timeservers experience very heavy traffic, which can affect your use of ClockWatch by bumping you off the queue. You may want to change the default timeserver you use if you continually experience an unreliable connection.
We've noticed this problem to be especially persistent with the following NIST timeservers:
Version 2.2.0 no longer uses any of these timeservers as a default and should not experience this problem.
An unresponsive timeserver affects users of ClockWatch by showing a "retrying connection to timeserver," or "No reply from server" message after attempting to set the time, accompanied by a failed attempt to synchronize the time.
To resolve this problem you must choose another timeserver. This is a simple procedure for Pro users, and a bit more complicated for Basic users because the Basic edition does not offer a feature to allow users to change the timeserver.
First determine your edition (Basic/Pro), open ClockWatch and Choose Help>About....
Pro users can change their timeserver by opening the software and choosing Options>Timeserver>Directory. From this directory, you can select any timeserver. Beagle Software recommends using utcnist.colorado.edu, or either ClockWatch timeserver maintained by Beagle Software. You can sort the list alphabetically or by protocol for easy review.
Version 2.2.0 defaults to utcnist.colorado.edu.
Basic users (prior to version 2.1.2) must run a utility (ClockWatch Basic Timeserver Modification Utility) to change the timeserver. If you notice an extended period in which the timeserver does not respond to ClockWatch Basic you might want to change the timeserver to which ClockWatch Basic is pointing.
Read below to download and review instructions on running this utility.
Changing the Timeserver
To change the timeserver you need to update the timeserver name in the registry. To change this, download the ClockWatch Basic Timeserver Modification Utility that can show and change the registry value for the current timeserver:
We apologize for this inconvenience and will do our best to anticipate NIST service interruptions in the future. Please feel free to write us with any tips or suggestions.