Windows PTP implementation on a Windows 10 Enterprise LTSC 1809 system

Question

Windows PTP implementation on a Windows 10 Enterprise LTSC 1809 system

Francesco S 0

Dear Support,

I am contacting you regarding an issue with the native Windows PTP implementation on a Windows 10 Enterprise LTSC 1809 system.

We are trying to synchronize the system clock of an industrial SBC to a NovAtel OEM7 GNSS receiver acting as a PTP Grandmaster over Ethernet.

The Ethernet connectivity is working correctly, but Windows Time Service does not detect the PTP time source and remains synchronized to the local CMOS clock.

System configuration

Operating System

Windows 10 Enterprise LTSC 1809

Build 17763

Ethernet adapter

Intel(R) I210 Gigabit Network Connection

Driver: 12.15.184.13

Driver date: 2019-11-25

NDIS: 6.50

Driver: e1r65x64.sys

Intel Ethernet Adapter Pack / PROSet 25.0

The I210 PTP-related NDIS parameters are enabled, including:

*PtpEnabled = 1

*PtpHardwareTimestamp = 1

*PtpHardwareTimestamping = 1

*SoftwareTimestamp = 1

*SoftwareTimestamping = 1

PTP Master

The PTP master is a NovAtel OEM7 GNSS receiver connected directly to the Intel I210.

Configuration:

PTP enabled

Profile: PTP_UDP

PTP Domain: 0

PTP over UDP/IPv4

IP address: 172.17.28.11

The device is reachable from Windows with no packet loss.

Windows PTP configuration

The native Windows PTP provider is enabled:

PtpClient\Enabled = 1

InputProvider = 1

DllName = C:\Windows\System32\ptpprov.dll

EnableMulticastRx = 1

AnnounceInterval = 1

DelayPollInterval = 0

Initially PtpMasters = 0.0.0.0 for master discovery.

As an additional troubleshooting step, we also tested explicitly setting:

PtpMasters = 172.17.28.11

NTP and VMICTimeProvider were disabled to avoid conflicts.

UDP ports 319 and 320 are allowed through the Windows Firewall.

Current result

The W32Time service starts correctly, but synchronization does not occur.

w32tm /resync /rediscover returns:

The computer did not resync because no time data was available.

w32tm /query /status /verbose reports:

Leap Indicator: 3 (not synchronized)
Stratum: 0 (unspecified)
ReferenceId: 0x00000000 (unspecified)
Last Successful Sync Time: unspecified
Source: Local CMOS Clock
State Machine: 0 (Unset)
Last Sync Error: 1 (The computer did not resync because no time data was available.)

We also noticed that the expected PTP event log does not exist:

Microsoft-Windows-Time-Service-PTP-Provider/Operational

and PtpClient/Operational is also not available.

The standard Windows Time Service log confirms that PtpClient is loaded and enabled, but there is no indication that PTP timing data is being received or processed.

Support requested

Could you please help us determine:

Is native PTP synchronization through PtpClient/ptpprov.dll fully supported on Windows 10 Enterprise LTSC 1809 (Build 17763)?

Is the Intel I210 with driver 12.15.184.13 / NDIS 6.50 supported for hardware PTP timestamping with W32Time on this Windows version?

Is our current PtpClient registry configuration correct for Windows 10 LTSC 1809?

Does Windows 10 LTSC 1809 require any specific PTP profile, transport, delay mechanism, or multicast configuration from the Grandmaster?

Is PTP over UDP/IPv4 supported with a NovAtel OEM7 configured as described above?

Is the absence of the PTP Provider Operational event log expected on this Windows version?

Is there a supported diagnostic method to determine whether ptpprov.dll is receiving PTP Announce/Sync/Follow_Up messages?

Are there any known issues with Windows 10 LTSC 1809 and Intel I210 PTP that could explain the State Machine: 0 (Unset) / no time data was available condition?

Please let us know which additional logs, commands, registry exports or packet captures you would like us to provide.

Thank you very much for your support.

Best regards,

FrancescoDear Support,