Hi,
You can refer to the other ways , and check if it works for you.
Windows 2016 Windows Time is not synching with external NTP server
We have 2 Active directory servers hosted using VMware Esxi 6.5, time synchronization is disabled in VMware.
We like to Synchronize time with our Fortigate firewall.
We tested the NTP server in Fortinet with the following command and find it is working.
w32tm /stripchart /computer:100.11.100.1 /samples:5 /dataonly
Tracking 100.11.100.1 [100.11.100.1:123].
Collecting 5 samples.
The current time is 10/13/2020 2:49:52 PM.
14:49:52, +00.0399737s
14:49:54, +00.0401130s
14:49:56, +00.0402340s
14:49:58, +00.0403350s
14:50:00, +00.0404899s
Then we configured external peer using
PS C:\Windows\system32> w32tm /config /syncfromflags:manual /manualpeerlist:"0.100.11.100.1,0x8" /update
The command completed successfully.
PS C:\Windows\system32> net stop w32time
The Windows Time service is stopping.
The Windows Time service was stopped successfully.
PS C:\Windows\system32> net start w32time
The Windows Time service is starting.
The Windows Time service was started successfully.
PS C:\Windows\system32> w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 1 (primary reference - syncd by radio clock)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0000000s
Root Dispersion: 10.0000000s
ReferenceId: 0x4C4F434C (source name: "LOCL")
Last Successful Sync Time: 10/13/2020 12:58:05 PM
Source: Local CMOS Clock
Poll Interval: 6 (64s)
Still the status shows Local CMOS Clock. Please advice how we can point ntp to our firewall.
Regards
Shijith
-
Fan Fan 15,361 Reputation points Microsoft Vendor
2020-10-14T00:43:06.68+00:00
2 additional answers
Sort by: Most helpful
-
Anonymous
2020-10-13T13:13:20.297+00:00 I'd try;
w32tm /unregister
net stop w32time
w32tm /register
net start w32time
w32tm /config /manualpeerlist:<ntp source> /syncfromflags:manual /reliable:yes /update
net stop w32time
net start w32time
then check the results
w32tm /query /source
w32tm /query /configuration
(I'd drop the
0x8
at least for testing)--please don't forget to Accept as answer if the reply is helpful--
-
Shijithkumar Pulassery 41 Reputation points
2020-10-15T08:11:11.77+00:00 Thanks @Anonymous & @Fan Fan
We finally able to solve it. There was a Group policy that was pointing NTP to an AD node. That was the issues.
Both reply was very helpful.
Thanks