WIndows 2022 Server - Cannot setup authoritative time, stuck on source=Local CMOS Clock

Question

I've been wrestling with this issue for a while. I cannot get NTP on the server to grab time from an Internet-based time server.

I have been able to use w32tm to run a stripchart of time.windows.com, so I believe the port is open.

I do not have any group policies on the system for Time.

The server is a bare metal one, a domain controller, running Windows Server 2022, and has the PDC role.

The source from w32tm always shows - "Local CMOS clock"

A w32tm resync command shows - "The computer did not resync because no time data was available."

Here is my configuration from w32tm:

[Configuration]

EventLogFlags: 2 (Local)
AnnounceFlags: 5 (Local)
TimeJumpAuditOffset: 28800 (Local)
MinPollInterval: 6 (Local)
MaxPollInterval: 10 (Local)
MaxNegPhaseCorrection: 3600 (Local)
MaxPosPhaseCorrection: 3600 (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: time.windows.com (Local)

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

Answer 1

Hello

Thank you for your question and reaching out. I can understand you are having query\issues related to Windows Time.

1. If this is VM then please try to disable Time Synchronization from VM Settings from Hyper-V.
2. Also Disable any Antivirus program or Windows firewall you may have for temporary purpose.
3. Run below commands -> Then reboot your Server. w32tm /unregister
   net stop w32time
   w32tm /register
   net start w32time
   w32tm /config /manualpeerlist:"0.ca.pool.ntp.org, 1.ca.pool.ntp.org, 2.ca.pool.ntp.org, 3.ca.pool.ntp.org" /syncfromflags:manual /reliable:yes /update
   net stop w32time
   net start w32time

--If the reply is helpful, please Upvote and Accept as answer--

Answer 2

I have been able to use w32tm to run a stripchart of time.windows.com, so I believe the port is open.

I don't remember the specifics but you could also wireshark it. Using the /stripchart switch ends up with a different port and I ended up finding the ISP was blocking UDP 123 in one direction.

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