On Wed Jan 17 06:13:56 2024 Luis Peromarta via samba <samba at
lists.samba.org>>
> I have the impression your DC?s ntp server is not working properly for
whatever reason. Your windows machines try to grab time for them, can?t, and
then default to local coms clock or some other time source.
>
> From a windows member machine, can you try :
>
> w32tm /stripchart /computer:us.pool.ntp.org /dataonly /samples:5
>
> That should work. Then try:
>
> w32tm /stripchart /computer:your.dc.address /dataonly /samples:5
>
> And see if you get a similar response.
> On Jan 16, 2024 at 20:31 +0100, Mark Foley <mfoley at
novatec-inc.com>, wrote:
> >
> > As I've mentioned, this time synchromization worked perfectly well
when this
> > same Windows domain member was connected to the Samba 4.8.2 domain.
Did you mean "us.pool.ntp.org"? That failed, but 0.pool.ntp.org
worked. So did
the one using my DC. I had actually tried that before and it worked before.
My latest attempt was the following, in PowerShell (based on yet another post):
stop-service w32time
w32tm /unregister
w32tm /register
start-service w32time
w32tm /config /manualpeerlist:0.pool.ntp.org /syncfromflags:manual /update
w32tm /config /reliable:yes
restart-service w32time
w32tm /resync
w32tm /query /source
Notice that I'm not using my DC as the time source, so whether that source
is a
problem is eliminated as a variable. After the 'w32tm /resync' I got
"the
computer did not resync because no time data was available." And the w32tm
/query /source is back to "Local CMOS Clock".
This is definitely a problem on the Windows end. I'm theorizing that perhaps
the switch of domain names from mail.hprs.local to dc1.hprs.locl could be the
problem. My next test will be to re-provision my DC with the old domain name,
restore the Windows back to when it was a member of that domain and see if
things are different.
As I keep mentioning, this all worked perfectly when this
same Windows domain member was time sourcing from the Samba 4.8.2 DC.