📎 AI Summary:
The original poster is experiencing issues with their Windows Server 2012 R2 domain controller not synchronizing time with an external NTP server (pool.ntp.org), instead remaining locked to the local CMOS clock, despite multiple configuration attempts and disabling VM time sync. A suggested solution from another user is to synchronize time directly on the VMware host, which is considered best practice. The original poster confirms that syncing the VMware host with the NTP server still results in a 5-minute delay, indicating ongoing synchronization problems.

VinsNg

New Member
Joined
Apr 12, 2018
Messages
2
Thread Author #1
Dear all, I'm configuring my domain controller (Windows Server 2012 R2) to be synchronized with pool.ntp.org but the w32time source still remain Local CMOS Clock.

- The PDC is a VM (VMware 6.0) and there is only this DC in the domain.
- I tried to use VM client to sync with NTP server and it is successful (I can see its port 123 UDP traffic from router NAT table), means the port didn't block. And the time for VM client has 5 minutes delay although synced with NTP server.
- already disabled VM client time synchronization to guest OS.
- Already restart and re-register the PDC w32time service, configure the pool.ntp.org peerlist successful, but when query status still pointing to Local CMOS Clock.
- When query configuration, type is 'NTP' and NTPServer is 'pool.ntp.org'
- No group policy about time server.
- Windows Firewall and antivirus already turned off
- Already checked the Windows Time registry of PDC from other domain and the settings are same.





Any idea how to resolve this?