[Samba] Samba4 Windows Client Time Sync Issue

[Luis Peromarta]

LP
On 27 Jun 2023 at 20:46 +0200, Marco Shmerykowsky PE via samba <samba at lists.samba.org>, wrote:
>
> Analyzing: -- -- (0 of 2)
> xxxx.xxxx.sce-engineers.com[xxx.xxx.xxx.xxx:123]:
> ICMP: 1ms delay
> NTP: -0.0009824s offset from xxxx.xxxx.sce-engineers.com
> RefID: (unknown) [0xFE00A8C0]
> Stratum: 4
> xxxx.xxxx.sce-engineers.com *** PDC ***[xxx.xxx.xxx.xxx:123]:
> ICMP: 1ms delay
> NTP: +0.0000000s offset from xxxx.xxxx.sce-engineers.com
> RefID: (unknown) [0xFE00A8C0]
> Stratum: 4
>
> Warning:
> Reverse name resolution is best effort. It may not be
> correct since RefID field in time packets differs across
> NTP implementations and may not be using IP addresses.
>
>
Your server marked as PDC means he holds the PDC role (one of 7 roles a DC can own). Otherwise DCs are all the same.

https://wiki.samba.org/index.php/Flexible_Single-Master_Operations_(FSMO)_Roles

The above suggests NTP servers in both DCs *may not* be working correctly. RefID represents the time source of that particular DC. Unknown may not be the best answer.

Could you try to get time in your DCs from the internet instead of your router and see if it helps ? I’ve just found in the past weeks chrony os so much easier and simpler than ntpd - could you try that ?

As an example, my output from command is as follows:

w32tm /monitor

bwing.mad.mater.int[192.168.0.13:123]:
    ICMP: 0ms delay
    NTP: -0.0009348s offset from awing.mad.mater.int
        RefID: pingless.com [178.215.228.24]
        Stratum: 3
> Results of w32tm /query /status on Working Client:
>
> Leap Indicator: 0(no warning)
> Stratum: 4 (secondary reference - syncd by (S)NTP)
> Precision: -23 (119.209ns per tick)
> Root Delay: 0.1429251s
> Root Dispersion: 1.9549461s
> ReferenceId: 0xC0A800FE (source IP: xxx.xxx.xxx.xxx)
> Last Successful Sync Time: 6/27/2023 1:16:43 PM
> Source: xxx.xxx.xxx.xxx,0x9
> Poll Interval: 10 (1024s)
>
> Phase Offset: 0.0000159s
> ClockRate: 0.0156249s
> State Machine: 2 (Sync)
> Time Source Flags: 0 (None)
> Server Role: 0 (None)
> Last Sync Error: 2 (The computer did not resync because only stale time
> data was available.)
> Time since Last Good Sync Time: 3080.4862280s
>
>

I am using W10 22H2 and the output is a lot shorter:

C:\Windows\system32>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 4 (secondary reference - syncd by (S)NTP)
Precision: -23 (119.209ns per tick)
Root Delay: 0.0258232s
Root Dispersion: 7.9589346s
ReferenceId: 0xC0A8000C (source IP:  192.168.0.12)
Last Successful Sync Time: 28/06/2023 09:21:48
Source: awing.mad.mater.int
Poll Interval: 10 (1024s)

Can you also try w32tm /resync /rediscover ?