samba - Jan 2024 - Joining Windows 10 Domain Member to Samba AD/DC

You think ntp works with samba but it doesn?t.

You *must* use chrony. It will take you exactly 5 minutes to get it up and
running.
On 5 Jan 2024 at 20:21 +0000, Mark Foley <mfoley at novatec-inc.com>,
wrote:
>
>
>
> How do you know you're syncing with the DC? What does your 'w32tm
/query /source'
> give you?
It?s all here :

http://samba.bigbird.es/doku.php?id=samba:install-chrony

On Fri Jan  5 18:54:48 2024 Luis Peromarta via samba <samba at
lists.samba.org> wrote:
>
> You think ntp works with samba but it doesn?t.
>
> You *must* use chrony. It will take you exactly 5 minutes to get it up and
running.
> On 5 Jan 2024 at 20:21 +0000, Mark Foley <mfoley at novatec-inc.com>,
wrote:
> >
> >
> >
> > How do you know you're syncing with the DC? What does your
'w32tm /query /source'
> > give you?
>
> It?s all here :
>
> http://samba.bigbird.es/doku.php?id=samba:install-chrony
I'm willing to give chrony a try. But ...

That doesn't explain why my w32tm /query /source gives me "Local CMOS
Clock".
That would have nothing to do with chrony, and indicates to me that the Windows
box isn't going to talk to the DC, period, whether it's running ntpd or
chrony.

I'm not sure I agree that ntp doesn't work with Samba. It has been
working with
samba for the past 10 years.

But, I'll install chrony shortly and see.

--Mark

On Fri, 5 Jan 2024 23:53:52 +0000
Luis Peromarta via samba <samba at lists.samba.org> wrote:
> You think ntp works with samba but it doesn?t.
Sorry, but 'ntp' does work, it is the rewrite for more security
'ntpsec' that doesn't seem to work.
> 
> You *must* use chrony. It will take you exactly 5 minutes to get it
> up and running. 
Chrony does seem to work, I just hope they do not follow ntpsec down
the same path.

The other thing that you have to know, Mark Foley is using Slackware,

Rowland