I think the headline sums it up nicely...
I have a PDC emulator (Windows Server 2022) that is running on a Hyper-V hypervisor that I'm trying to sync to the correct time. The server always runs about 5 minutes fast, even after telling it to sync with the NTP server pools (time.nist.gov and pool.ntp.org). I'll get Event ID 261 where it'll tell me that it's successful in synching the time, but it's still just under 5 minutes fast.
Except for maybe 1 second every time it tries to sync. It will show the CORRECT time for just that 1 second, then revert back to the incorrect time.
I tried w32tm /stripchart as well, and it gives me error 0x800705B4. Adding the /packetinfo flag gives the reference and originate timestamps as 0 (well 0x00000000etc0) which is odd.
I've tried a packet trace, and the server (client) is communicating with the NTP server.
w32tm /query /status/verbose
Leap Indicator: 0(no warning)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Precision: -23 (119.209ns per tick)
Root Delay: 0.0751364s
Root Dispersion: 266.0852887s
ReferenceId: 0x84A36102 (source IP: 132.163.97.2)
Last Successful Sync Time: 2/19/2025 7:12:31 AM
Source: time.nist.gov,0x8
Poll Interval: 7 (128s)
Phase Offset: -0.0000053s
ClockRate: 0.0156250s
State Machine: 3 (Spike)
Time Source Flags: 0 (None)
Server Role: 576 (Reliable Time Service)
Last Sync Error: 0 (The command completed successfully.)
Time since Last Good Sync Time: 7.9033052s
Any ideas what's going on here? How can I fix this? What else can I look at?
Thanks!
