NTP Sync Issue

Question

Hello all,

I have 2 DCs "2019" i configured the primary DC "holding PDC" as NTP server by running the following commands:

w32tm /config /manualpeerlist:dc1.com,0x8 /syncfromflags:manual /reliable:yes /update

Then i run: The command completed successfully.

C:\Users\Administrator>w32tm /resync /rediscover
Sending resync command to local computer
The command completed successfully.

C:\Users\Administrator>net stop w32time && net start w32time
The Windows Time service is stopping.
The Windows Time service was stopped successfully.

The Windows Time service is starting.
The Windows Time service was started successfully.

Then i run: w32tm /query /source
dc1.com.local,0x8

C:\Users\Administrator>w32tm /query /configuration
[Configuration]

EventLogFlags: 2 (Local)
AnnounceFlags: 5 (Local)
TimeJumpAuditOffset: 28800 (Local)
MinPollInterval: 6 (Local)
MaxPollInterval: 10 (Local)
MaxNegPhaseCorrection: 172800 (Local)
MaxPosPhaseCorrection: 172800 (Local)
MaxAllowedPhaseOffset: 300 (Local)

FrequencyCorrectRate: 4 (Local)
PollAdjustFactor: 5 (Local)
LargePhaseOffset: 50000000 (Local)
SpikeWatchPeriod: 900 (Local)
LocalClockDispersion: 10 (Local)
HoldPeriod: 5 (Local)
PhaseCorrectRate: 7 (Local)
UpdateInterval: 100 (Local)

[TimeProviders]

NtpClient (Local)
DllName: C:\Windows\system32\w32time.dll (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)
AllowNonstandardModeCombinations: 1 (Local)
ResolvePeerBackoffMinutes: 15 (Local)
ResolvePeerBackoffMaxTimes: 7 (Local)
CompatibilityFlags: 2147483648 (Local)
EventLogFlags: 1 (Local)
LargeSampleSkew: 3 (Local)
SpecialPollInterval: 1024 (Local)
Type: NTP (Local)
NtpServer: dc1.com,0x8 (Local)

NtpServer (Local)
DllName: C:\Windows\system32\w32time.dll (Local)
Enabled: 1 (Local)
InputProvider: 0 (Local)
AllowNonstandardModeCombinations: 1 (Local)

VMICTimeProvider (Local)
DllName: C:\Windows\System32\vmictimeprovider.dll (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)

The issue is not all servers getting the time from dc1 "NTP server". for example:

What else can i do to fix this issue.

Thank you

Answer 1

Did not work unfortunately. it keeps taking server battery. It worked after i applied the solution on the following article:

https://theitbros.com/configure-ntp-time-sync-group-policy/

it worked only via group policy NOT CMD by adding :

us.pool.ntp.org,0x1 1.us.pool.ntp.org,0x1 2.us.pool.ntp.org,0x1 3.us.pool.ntp.org,0x1;

then followed mentioned steps on the article.

Thank you

Answer 2

All our server are VMs "including DCs"

Answer 3

Seems a little odd pointing the PDC emulator to another domain controller (dc1)? In this case using NT5DS may be more apropriate.

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/

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

Answer 4

DC1 is the primary domain controller "PDC". some servers pointing to it, others not

Answer 5

Then I guess it sounds like you're trying to point the "PDC" to itself? Generally you'll want the PDC emulator to point to an external NTP source.
https://tf.nist.gov/tf-cgi/servers.cgi

https://blogs.technet.microsoft.com/nepapfe/2013/03/01/its-simple-time-configuration-in-active-directory/

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