Testing & Troubleshooting

Home Downloads Order  

Site Map
Tech Info



ClockWatch Client/Server




ClockWatch Product FamilyTimeserver Test
Testing & Troubleshooting




ClockWatch Client/Server
 Self Test

Client/Server communication features two way data exchange between the time client and the time server.    When testing a Client/Server connection it is necessary to look at both ends of the conversation.

ClockWatch Client/Server keeps a network in sync

If you are experiencing problems, then you should check both the client and server ends of the exchange as well as the connection between the two. The Client/Server self test allows you to simulate the client communication from the timeserver itself.

Client/Server Self Test

ClockWatch includes  a client/server self test. This checks to see if the basic time server functionality for the program is working by making a client time request from the same computer. It is accessed from the Client options tab in ClockWatch.

Test Features

  •  Checks time serving functionality of ClockWatch running on computer.

  •  Simulates a time request coming from another computer on a network

  •  Aids in pinpointing network communication and access problems with clients communicating with server.

Clientscreen (Client Server test screen)


Server Section        
Current port and protocol settings in ClockWatch for serving time to clients currently being tested.

Localhost refers to the current machine and resolves to This is also called a loopback test.

Time-sync protocol used to communicate with clients.

Number of TCP or UDP
port used to communicate with clients.

Time Services
Shows the status of the ClockWatch and Windows Time service. ClockWatch service is a background process that runs whenever Windows is running. It can be on or off for the test.
Windows time is the native time client in Windows.
Note: If using SNTP protocol to serve time in ClockWatch, the Windows Time service should NOT be running.

Client Section        
Communicates with timeserver by sending a time request in the given protocol.

Tests Available:

Resolve name
Check that localhost can be resolved to an IP address (

Common connection test to verify ability of this computer to respond to pings. The ping utility uses the ICMP echo request and echo reply packets.

Time-sync protocol used to communicate with the timeserver using the NIST protocol.

Common time-synchronization protocol.

Simple Network Time Protocol

Time protocol, TCP connection time.

Time protocol, UDP connection type. Also called net date.

Protocol used in the test to run. This should be same as the server.

Whether the test uses a TCP or UDP type connection.

Port number used to communicate with timeserver in test. This should be the same port as the server.

Toggle all tests on or off.

Timeout Interval
Interval in seconds to wait for the timeserver to respond for each test.  If the server does not respond within the interval, then the test fails.

Test Results Section

Shows the results of the communications tests.

Pass (Gd) Test Checkmark
The timeserver has responded to the test with the appropriate response

Fail (Bd) Test Checkmark
The timeserver has failed to respond to the test on the port specified, or the response was in an unexpected format

The string returned by the timeserver or the results of the test


Troubleshooting Client/Server Problems using the self test 


Client/Server Self Test
The Client/Server self test shows if the timeserver is running and able to reply to a client request running on the same computer. If the test passes it indicates that the basic time functionality is running.

It is recommended that you run this test if you are having any problems in reaching the timeserver from a client computer.

If the self test passes but you can't connect from another time client on the network, check:

  1. address of timeserver, must be name or IP of this computer

  2. protocol (i.e. SNTP) and port (i.e. 123), client protocol and port must match server

  3. if firewalls running on client or server that are blocking communication on the port used. Try turning off the firewall to see if client/server can communicate. If they do then you can reconfigure the firewall to allow communication on the port.

If the self test fails, check:

  • Conflict of another program running on the same port. (i.e. Windows time service running when you are running SNTP protocol in ClockWatch) . To check for port conflicts, stop ClockWatch Service, exit ClockWatch and run netstat -a from the DOS command line.  Check for other occurrences of the port number in use in the list.

Self Test and firewalls:

  • Running the self test does not exercise the firewall since all communication stays on the host computer.

For more information

See also:

Client/Server Troubleshooter
ClockWatch behind firewalls
Multi-Platform configuration

Product Information
   Detailed Product Guide

   Advanced Features
   Client/Server Description
   User GuideInstallationFAQ
   User and Editorial Comments Support

ClockWatch Product Index


Related Products
ClockWatch Enterprise- provides central time monitoring and control
See Also
Star Sync - Secure and Accurate GPS Time Source

ClockCard - precise clock on a PC card