THIS PAGE REFERS TO AN OLDER VERSION OF DOMAIN TIME. CLICK HERE FOR INFORMATION ON THE CURRENT VERSION.
This page allows you to control the broadcast behavior of the Domain Time II Server. By default, Domain Time II Server only uses network
broadcasts to send cascade and advisory messages to Slaves and Clients to ensure time is propagated correctly throughout the network.
However, if required, you may also set the Server to send out periodic time sync broadcasts for clients (Domain Time or other third-party
clients) that understand broadcast time.
The Domain Time II Control Panel Applet - Broadcast Time Tab
Domain Time II Control Broadcasts
Domain Time II uses a highly efficient time distribution hierarchy to ensure that time is distributed and updated extremely accurately across the network.
This is accomplished by communication among the various Domain Time components using accurate time protocols and special synchronization control messages
(see Cascading Time Hierarchy for details).
This section allows you to set whether the Server will send these control messages to its slaves and clients. Caution: Modifying these entries can
have a significant effect on the overall accuracy of your network time. Modify them with care.
Enable Cascade Signals
When this checkbox is checked, Server will send Cascade triggers to its slaves and/or clients. Cascade triggers inform the recipient that they must
synchronize with their time source immediately, and if they have slaves or clients of their own, to instruct them to synchronize immediately as well.
Enable Advisory Signals
When this checkbox is checked, Server will send Advisory messages to its slaves and/or clients. Advisory messages inform the recipient that the server
has recently synchronized its time and that the component should synchronize its time as soon as possible.
Domain Time II Server can provide two types of Broadcast Time - Heartbeats (using the Domain Time II UDP protocol) and/or NTP Broadcasts (using the NTP UDP protocol).
Using Broadcast Time can have significant consequences to your network; be sure you understand these options before enabling them. See the
When to use Heartbeats and NTP Broadcasts page for a detailed discussion of these options.
You should never have more than one time server (whether Domain Time II or a third-party product) providing time broadcasts on the same network! Severe adverse consequences to your network's time
can result, including the potential for clock reversals. Although you can configure Domain Time clients to prevent them from responding to rogue broadcasts,
other clients may be severly confused by multiple broadcasts.
Domain Time II Heartbeats
When this checkbox is checked, Server will send Heartbeats of the type you select using the radio buttons, on the schedule you specify using the selection boxes.
Advisory only (2.5 compatible)
For Domain Time components version 2.5 and later. When a Client receives a Domain Time II Heartbeat pulse, it will immediately attempt to synchronize with its
server (which is not necessarily the machine providing the pulse). The main advantage to this method is that a Client can never use an incorrect time
source as a result of the broadcast. The disadvantage is that it is less efficient than broadcasts that include time information since the client is required
to request a time update from its source.
Send time information
Domain Time Version 3.1 and later. Time sync data is included in the Heartbeat broadcast packet itself, and a Client will immediately set its time to match the
packet. This results in significantly lower overhead than the Advisory Only Heartbeat. This is the ideal selection to use with the
Ultra Thin Client.
The only potential disadvantage to this method is that an unconfigured client could potentially respond to conflicting broadcasts from other
broadcasting servers. However, Domain Time Clients can be configured to only accept time broadcasts from specified servers to prevent this issue.
Set the schedule to the maximum period that provides the accuracy you require. Setting the broadcast to occur too often can actually degrade accuracy by
creating too much network traffic and system overhead.
NTP Time BroadcastsEnable NTP Time Broadcasts
When this checkbox is checked, Server will send NTP Broadcasts on the schedule you specify using the selection boxes.
Use NTP Broadcasts only if you have third-party clients on the network that require them. The NTP Broadcast Version drop-down box lets you select the
version of NTP Broadcast to be sent (for compatilibity with various clients). Choose the version your client(s) require.
Set the schedule to the maximum period that provides the accuracy you desire. Setting the broadcast to occur too often can actually degrade accuracy by
creating too much network traffic and system overhead.
Important: Domain Time II Server's ability to serve NTP is disabled by default when Server is installed on a Windows Active Directory Domain Controller.
On those machines, the Windows Time service is set to provide NTP for compatibility with Windows Time clients using the NT5DS sync mode.
You will not be able to send NTP Broadcasts from a Active Directory DC unless the NTP server portion of Windows Time service is disabled on that machine.
This will require any Windows Time clients on the network to be changed from NT5DS to NTP Client sync mode. See the
Co-existing with Windows Time page for a complete explanation.