Correcting time source on a non-PDC-emulator DC

Question

Hi,
I've discovered a time difference On a DC running windows server 2019 that is not a PDC emulator. Checking its time source shows that it does not follow the domain hierarchy and depends on the local CMOS as follows:

w32tm /query /status
Leap Indicator: 3(not synchronized)
Stratum: 0 (unspecified)
Precision: -23 (119.209ns per tick)
Root Delay: 0.0000000s
Root Dispersion: 0.0000000s
ReferenceId: 0x00000000 (unspecified)
Last Successful Sync Time: unspecified
Source: Local CMOS Clock
Poll Interval: 6 (64s)

Then I tried to "reset" the time service using:
net stop w32time
w32tm /unregister
w32tm /register
net start w32time

w32tm /config /syncfromflags:domhier /update
net stop w32time
net start w32time

I found Two issues:

1- During stopping windows time service I get an error as follows:

net stop w32time
The Windows Time service is stopping.
A system error has occurred.

System error 23 has occurred.

Data error (cyclic redundancy check).

The Windows Time service was stopped successfully.

2- The time source is not changed to follow the domain hierarchy.

any ideas?

Answer 1

Hi,

Starting with basic;
Check if you have UDP port 123 open between ntp server and ntp clients
Try configure service manually "w32tm /config /manualpeerlist:[server],0x8 /syncfromflags:MANUAL /reliable:yes /update" -- > flag "0x8" force normal "client" request and not "symmetric active" requests, then w32tm /config /update.

Additional commands to trobleshoot (also look for IMPORTANT event viewer events
net time /querysntp
net stop w32time
w32tm /unregister
w32tm /register
W32tm /resync /rediscover
net start w32time

Answer 2

Some general info

• All domain members should use NT5DS domain time.
• Desktops and member servers sync with any domain controller.
• Domain controllers sync with PDC emulator (one per domain)
• PDC emulator in child domain can sync with any domain controller in parent domain.
• PDC emulator in parent domain syncs with either a hardware clock or possibly an external source.
  https://blogs.technet.microsoft.com/nepapfe/2013/03/01/its-simple-time-configuration-in-active-directory/

For the problem member you can

w32tm /unregister
net stop w32time
w32tm /register
net start w32time
w32tm /config /syncfromflags:domhier /update
net stop w32time
net start w32time
then check
w32tm /query /source
w32tm /query /configuration

--please don't forget to upvote and Accept as answer if the reply is helpful--