- Network conditions
- The accuracy of the computer's hardware clock
- The amount of CPU and network resources available to the Windows Time service
![Ntp Ntp](https://i0.wp.com/2.bp.blogspot.com/-0OnIGI3D9do/VL8APkxKfpI/AAAAAAAADm0/aP74kCmnPp4/s1600/1-20-2015%2B8-10-40%2BPM.png)
Windows Time Service Architecture
- Service Control Manager
- Windows Time Service Manager
- Clock Discipline
- Time providers
- Input providers request and receive time samples from configured NTP time sources.
- These time samples are then passed to the Windows Time Service Manager, which collects all the samples and passes them to the clock discipline subcomponent.
- The clock discipline subcomponent applies the NTP algorithms which results in the selection of the best time sample.
- The clock discipline subcomponent adjusts the time of the system clock to the most accurate time by either adjusting the clock rate or directly changing the time.
Windows Time Service Time Protocols
Network Time Protocol
NTP Algorithms
NTP Time Provider
- NtpServer output provider. This is a time server that responds to client time requests on the network.
- NtpClient input provider. This is a time client that obtains time information from another source, either a hardware device or an NTP server, and can return time samples that are useful for synchronizing the local clock.
NTP Security
Hardware Devices That Are Supported by the Windows Time Service
Simple Network Time Protocol
Time Protocol Interoperability
Windows Time Service Processes and Interactions
- Domain hierarchy-based synchronization
- A manually-specified synchronization source
- All available synchronization mechanisms
- No synchronization.
Domain Hierarchy-Based Synchronization
Reliable Time Source Configuration
Time Source Selection
- Additional synchronization cycles.
- Increased volume in network traffic.
![Synchronize Time With Ntp Server Synchronize Time With Ntp Server](/uploads/1/2/4/3/124351825/443886105.jpg)
- If the computer is not a member of a domain, it must be configured to synchronize with a specified time source.
- If the computer is a member server or workstation within a domain, by default, it follows the AD DS hierarchy and synchronizes its time with a domain controller in its local domain that is currently running the Windows Time service.
- A reliable time source can only synchronize with a domain controller in the parent domain.
- A PDC emulator can synchronize with a reliable time source in its own domain or any domain controller in the parent domain.
Query Number | Domain Controller | Location | Reliability of Time Source |
---|---|---|---|
1 | Parent domain controller | In-site | Prefers a reliable time source but it can synchronize with a non-reliable time source if that is all that is available. |
2 | Local domain controller | In-site | Only synchronizes with a reliable time source. |
3 | Local PDC emulator | In-site | Does not apply. A domain controller does not attempt to synchronize with itself. |
4 | Parent domain controller | Out-of-site | Prefers a reliable time source but it can synchronize with a non-reliable time source if that is all that is available. |
5 | Local domain controller | Out-of-site | Only synchronizes with a reliable time source. |
6 | Local PDC emulator | Out-of-site | Does not apply. A domain controller does not attempt to synchronize with itself. |
- A computer never synchronizes with itself. If the computer attempting synchronization is the local PDC emulator, it does not attempt Queries 3 or 6.
Domain Controller Status | Score |
---|---|
Domain controller located in same site | 8 |
Domain controller marked as a reliable time source | 4 |
Domain controller located in the parent domain | 2 |
Domain controller that is a PDC emulator | 1 |
Manually-Specified Synchronization
All Available Synchronization Mechanisms
Stopping Time Synchronization
Disabling the Windows Time Service
Network Ports Used by Windows Time Service
Sync Time With Ntp Server Windows 10
Service name | UDP | TCP |
---|---|---|
NTP | 123 | N/A |
SNTP | 123 | N/A |
See Also
You can synchronize an event broker’s clock with a networked Network Time Protocol (NTP) server. This is especially helpful for event brokers that are using redundancy and/or Replication. For example, if your event brokers are synchronized with the same NTP server, message expiry times will be consistent across all of them.
The procedure for synchronizing with an NTP server differs for appliances and software event brokers.
Synchronize Time With Ntp Server Ip
Appliances
An appliance can be time synchronized using either the set up commands explained in Initial Set Up, or using the clock synchronization CLI commands shown below:
solace(configure)# clock
solace(configure/clock)# synchronization
solace(configure/clock/synchronization)# shutdown
solace(configure/clock/synchronization)# protocol ntp
solace(configure/clock/synchronization)# ntp-server <ip-addr>
solace(configure/clock/synchronization)# no shutdown
Where:
ip-addr
is the IP address or fully qualified domain name (FQDN) of a reachable NTP server.
The no
version of this command, no ntp-server
, removes the NTP server information.
: If you need to reset the clock synchronization protocol to NTP, use the command solace(configure/clock/synchronization)# no protocol
Software Event Brokers
Software event broker clocks can be synchronized with one of the three methods shown in the following list.
: With the PubSub+ AWS AMI, clock synchronization is preconfigured to use AWS time servers. Use chronyd
to change the clock server.