This page controls the client portion of Net Time Server & Client operation. In the page, you can change many of the global settings that affect all of unicast/manycast mode and broadcast/multicast mode clients using the NTP/SNTP, Time or UnixTime protocol. To access this "Client" page, select the "Client" item from the tree menu on the left side of the "Main window".
The section allows you to specify a number of settings for all of the NTP/SNTP, Time and UnixTime clients, including unicast/manycast and broadcast/multicast mode.
Check the box, The Net Time Server & Client will send a notification message to all applications curently running after each successful synchronization, notifying them that the system clock has changed.
Checking this box will cause the Net Time Server & Client to automatically terminate after a successful synchronization operation.
If the "Exits after synchronization" box is checked, you can check this box. It will cause the Net Time Server & Client to automatically terminate after a synchronization operation, even if it is fail.
In general, the client will immediately correct the system clock when synchronizing. It may cause the system clock to jump noticeably when adjustments are made. Checking the box causes the client adds a time increment to system clock at each clock interrupt when synchronizing until the system clock is synchronized. It avoids the system clock to jump noticeably when adjustments are made.
Specifies a period for periodic time adjustment. The system clock will be synchronized whthin the period.
Specifies the maximum clock speed increment/differential in percent of the current clock speed for periodic time adjustment. The clock speed increment/differential that will be add to the system clock will less than the value when synchronizing.
Check the box to check the local time offset when synchronizing. The response packet or broadcast/multicast packet that is received from server will be discarded if the local time offset value is greater than maximum adjust offset value specified below. This check avoids using a deviant response packet or a deviant broadcast/multicast packet to correct the system clock.
Specify the maximumtime offset value for checking time offset before synchronization. The response packet or broadcast/multicast packet that is received from server will be discarded if the local time offset value is greater than the maximum adjust offset value.
Checking the box will cause the client not to check the local time offset when first synchronization. It avoids to block the client if local time offset is greater than maximum adjust offset value when start the Net Time Server & Client.
The section allows you to specify a number of settings for the client that use the NTP/SNTP protocol. Unless expressly specified, including unicast/manycast and broadcast/multicast mode.
This reference timestamp field in the NTP/SNTP packet that is received from NTP/SNTP server (unicast/manycast response or broadcast/multicast packet) is the time the system clock was last set or corrected. Checking the box will cause the client to check the reference timestamp field in the NTP/SNTP packet that is received from NTP/SNTP server (unicast/manycast response or broadcast/multicast packet). This check avoids using a server whose synchronization source has expired for a very long time.
Specify the maximum expired period value for checking the reference timestamp field in the NTP/SNTP packet that is received from NTP/SNTP server (unicast/manycast response or broadcast/multicast packet).
The root delay field in the NTP/SNTP packet that is received from NTP/SNTP server (unicast/manycast response or broadcast/multicast packet) indicates the total roundtrip delay to the primary reference source from server. Checking the box will cause the client to check the root delay field when synchronizing. The NTP/SNTP packet that is received from NTP/SNTP server (unicast/manycast response or broadcast/multicast packet) will be discarded if the root delay value is less than 0 or greater than maximum delay specified below. This check avoids using a server whose synchronization source has long network delay.
Specify the maximum root delay value for checking the root delay field in the NTP/SNTP packet that is received from NTP/SNTP server (unicast/manycast response or broadcast/multicast packet).
The root dispersion field in the NTP/SNTP packet that is received from NTP/SNTP server (unicast/manycast response or broadcast/multicast packet) indicates the maximum error due to the clock frequency tolerance of its primary reference source. Checking the box will cause the client to check the root dispersion field when synchronizing. The NTP/SNTP packet that is received from NTP/SNTP server (unicast/manycast response or broadcast/multicast packet) will be discarded if the root dispersion value is less than 0 or greater than maximum dispersion specified below. This check avoids using a server whose synchronization source accuracy is not enough.
Specify the maximum root dispersion value for checking the root dispersion field in the NTP/SNTP packet that is received from NTP/SNTP server (unicast/manycast response or broadcast/multicast packet).
For unicast/manycast client, the version field in the NTP/SNTP server reply should match the version field used in the NTP/SNTP client request, otherwise the reply will be discarded. For broadcast/multicast client, the version number in "Client - Broadcast/Multicast" page should match the version field in the NTP/SNTP broadcast/multicast packet sent from NTP/SNTP broadcast/multicast server, otherwise the packet will be discarded. Checking the box will cause the unicast/manycast client and the broadcast/multicast client not to check about these.
When the IP source and destination addresses are available for the NTP/SNTP client request, they should match the interchanged addresses in the NTP/SNTP server reply. Also, when the UDP source and destination ports are available for the NTP/SNTP client request, they should match the interchanged ports in the NTP/SNTP server reply, otherwise the reply will be discarded. Checking the box will cause the unicast/manycast client not to check about these.
The option is only used in unicast and manycast modes.
For unicast/manycast client, The originate timestamp field in the NTP/SNTP server reply should match the transmit timestamp field used in the NTP/SNTP client request, otherwise the reply will be discarded. For broadcast/multicast client, the The originate timestamp field in the NTP/SNTP broadcast/multicast packet sent from NTP/SNTP broadcast/multicast server should equal to zero, otherwise the packet will be discarded. Checking the box will cause the unicast/manycast client and the broadcast/multicast client not to check about these.
The NTP/SNTP packet that is received from NTP/SNTP server (unicast/manycast response or broadcast/multicast packet) should be discarded if the leap second flag field is 3, it indicates that the NTP/SNTP server is unsynchronized. Checking the box will cause the client not to check about this.
The stratum field in the NTP/SNTP packet that is received from NTP/SNTP server (unicast/manycast response or broadcast/multicast packet) is an indication to show the level of accuracy of this server clock. The NTP/SNTP specification allows a number from 1 to 15. If the stratum field is 1, indicating a primary server and most accurate. If the stratum field is 2 to 15, indicating a secondary server. If the stratum field is 0, indicating that the packet is a KoD message (RFC-4330, unicast and manycast modes), or indicating that the server isn't synchronized (RFC-2030). In general, an client that use the NTP/SNTP protocol should stop sending to a particular server if that server returns a reply with a stratum field of 0, and the NTP/SNTP packet that is received from a NTP/SNTP server (unicast/manycast response or broadcast/multicast packet) will be discarded if the stratum field is not within 1 to 15. Checking the box will cause the client not to check about this.
The KoD packet is useful to tell clients to stop sending request packets that violate server access controls.
Check the box to deactivate the source NTP/SNTP server in "Source servers queue" in "Client - unicast/manycast" page if it reply a KoD message, and to stop sending request packets to the NTP/STNP server.
The option is only used in unicast and manycast modes, and RFC-4330 protocol.
Specifies the local clock precision for the client that use the NTP/SNTP protocol to calculate the local time offset. It's about 50 milliseconds (-4: 64 milliseconds) for Windows 95/98/Me, and it's about 10 milliseconds (-6: 16 milliseconds) for Windows NT4/2000/XP/2003/Vista.
With this button you will load the default configuration of the page.
You need to press the "Apply" button for saving the default configuration.
With this button you will accept and save current configuration.
With this button you will cancel current configuration and rollback to previous one.