Technical Support
Troubleshooting
ClockWatch won't make time setting
Check that the connection to the Internet is working by opening a Web browser.
Open your Web browser and test Internet connection by opening a web page.
There is no Internet connection to the timeserver selected. Verify the connection to the timeserver by using Telnet
Look for errors in the NIST log window that indicate a setting can't be made due to the NIST server being down or other causes.
Too many requests have been made to the NIST over a short period of time.
Change the NIST server used under the Options menu or wait 15 minutes before retrying.

ClockWatch is installed behind a firewall
ClockWatch needs to be properly configured to work behind a proxy server.
As a test, check to see if your Web browser is configured to work with a proxy server. If so, see the section in the ClockWatch User Guide about configuring ClockWatch to work behind firewalls.

ClockWatch makes the wrong time setting
If the NIST format is being used, check the Control panel to check the time zone setting in the Time/Date menu. ClockWatch uses the Windows internal time zone setting to determine if daylight savings time is both used and in effect.
Check time zone in the Date/Time control panel
If a Daytime type timeserver is used then check that the hours difference field is set correctly.

Settings aren't being made by ClockWatch
System clock is accurate and in sync.
Setting attempts are being made too close together and no adjustment is needed.
There is no Internet connection to the timeserver selected. Verify the connection to the timeserver by using Telnet.
System is set in the Manual mode and no settings have been made.

Graphs don't show anything
No clock settings have been needed: difference and accuracy are both "0"
No reading has been made since startup.
The log file has not been specified or is turned off (Previous Settings Graph only)

Registration screen appears at startup
Software has not yet been registered: registered software will skip the Registration screen.
The Windows System Registry has been altered or corrupted. Re-enter the Key Code to re- register the software.

'Address in Use' or 'Can't Reset Server' Error Messages (CW Server)
Is usually due to the TCP port that the Client Server communication normally uses is being used by another application. ClockWatch uses port 1001 for Client Server communication. If another application is using this port then ClockWatch is unable open it and complains.
The address can be changed on both the Client and the Server, please contact Beagle Software support for instructions.

Clock drift numbers vary widely
There is a process or hardware that is causing the clock to loose or gain  (generally loose) time at a faster rate then at other times.
The system is very busy and the clock is loosing time at a faster rate then normal.

There is no time difference shown after a setting
The difference in time with the measurements have been too small (1 second or less) to make a clock setting.