PTP in Windows Server 2019

Question

I configured the built in ptpclient to receive multicast from a PTP grandmaster clock. W32TM logs 512 and 513 events in timeservice-ptp event folder. So all seems to be fine except the ptpprov.dll is thinking the ptp time is a huge negative offset to current time. See w32tm debug logs below......anyone know what is causing this? we use the same multicast for PTP in ubuntu without issue.

153371 18:37:17.3839611s - W32TmServiceMain: ********** Time Slip Notification **********
153371 18:37:17.3839790s - USO:0.000000000 URA:0.000000000 UO:0 kPHO:0 spO:935632303632
153371 18:37:17.3839945s - ClockDispln TimeSlip:TimeSlip LastUTC:501573 SetUnsync: LI:3 S:0 RDl:0 RDs:0 TSF:0x0
153371 18:37:17.3840108s - UpdateTimerQueue1: TN:78370780000::: LRT:75336090000 LUT:78370780000 LAFLTNS:0 TSLGT:0 LTNS:864000000000
153371 18:37:17.3840189s - W32TmServiceMain: waiting i16.000s (64.000s)
153371 18:37:17.9696677s - W32TmServiceMain: resync req, user requested, get samples as soon as possible.
153371 18:37:17.9696841s - UpdateTimerQueue1: TN:78376560000::: LRT:75336090000 LUT:78370780000 LAFLTNS:5780000 TSLGT:5856480 LTNS:864000000000
153371 18:37:17.9696905s - W32TmServiceMain: waiting i0.000s (63.414s)
153371 18:37:17.9697071s - W32TmServiceMain: timeout
153371 18:37:17.9697218s - PtpClient returned 1 samples.
153371 18:37:17.9697279s - Intersection successful with 0 dropped samples.
153371 18:37:17.9697342s - 0: Sample:0 SyncDist:4017120001454181 SelectDisp:0
153371 18:37:17.9697398s - Sample 0 chosen. Select Dispersion:00.0000000s SPHO:0 STC:501610
153371 18:37:17.9697479s - Sample 0 offset:-803423938.4763952s delay:+803423936.2908323s dispersion:00.0000020s
153371 18:37:17.9697647s - USO:0.000000000 URA:0.000000000 UO:0 kPHO:0 spO:935632303632
153371 18:37:17.9697722s - ClockDispln Update: LastUTC:501610 SO:-8034239384763952 KPhO:0 spO:935632303648 *PhO:-8034239384763952 uT:37
TOO BIG Unset->Hold
153371 18:37:17.9697995s - Logging error: The time service has detected that the system time need to be changed by -18446744072906127678 seconds. For security reasons, the time service will not change the system time by more than -4294967295 seconds. Verify that your time and time zone are correct, and that the time source 10.22.238.254 is working properly.

Answer 1

Looks like the W32TmServiceMain: timeout may be a problem. Something here may help.
https://techcommunity.microsoft.com/t5/networking-blog/windows-subsystem-for-linux-for-testing-windows-10-ptp-client/ba-p/389181

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

Answer 2

Hi,
The time limit 4294967295 seconds seems to be controlled by the Registry key
"MaxPosPhaseCorrection"=dword:0000d2f0
and
"MaxNegPhaseCorrection"=dword:0000d2f0
under [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config] hive
You should be able to adjust this value.
Clients are configured to use a setting of 300 seconds (five minutes), which is a default setting that is part of the Kerberos security model.
Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl