I'm trying to set up a domain controller as an NTP server for my organization, but I'm running into issues. Each time I check its status, it's still showing the CMOS clock instead of syncing properly. I've rebooted the server and attempted to start from scratch, but the problem persists. I've also disabled time synchronization in Hyper-V, just in case anyone might ask about that. I'm looking for suggestions and guidance on the best way to get this NTP server running correctly. Thanks for your help!
4 Answers
It's crucial to decide on an external time source for your domain controller, ideally a Stratum 1 time server like pool.ntp.org. You can then set your primary DNS server to sync with this Stratum 1 source. Your clients will sync with the PDC emulator, which you can set as a Stratum 2 server.
Whenever I tackle this kind of issue, I rely on the official Microsoft guidelines for setting up an NTP server. They have clear instructions to follow. Make sure to configure your DC correctly and then ensure all other devices point back to this DC as the time source for everyone in your network, creating a single source of truth.
If you're running NTP inside a VM, that might be the source of your problems. I strongly recommend running your NTP server directly on bare metal instead. Virtual machines can introduce instability, which can lead to synchronization issues.
You mentioned having issues with external time sources. If your DC doesn't have an external source configured, it will default to its internal hardware clock. So, definitely check which external time source you have set up to sync with the domain controller.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures