similar to: The care and feeding of the signing socket; also NTPsec

On Thu, 19 Sep 2024 06:44:13 -0700 (PDT) James Browning via samba <samba at lists.samba.org> wrote: > TLDW: I have a Samba install, and I can use help getting the signing > socket to return a signature with either Chrony or NTPsec; I would > appreciate some guidance on what I am doing incorrectly. I partially > followed the instructions at [1]; after checking and revising, I saw

On 9/19/24 09:23, Rowland Penny via samba wrote: > On Thu, 19 Sep 2024 06:44:13 -0700 (PDT) > James Browning via samba <samba at lists.samba.org> wrote: > >> TLDW: I have a Samba install, and I can use help getting the signing >> socket to return a signature with either Chrony or NTPsec; I would >> appreciate some guidance on what I am doing incorrectly. I

On Thu, 19 Sep 2024 17:29:49 -0500 samba via samba <samba at lists.samba.org> wrote: > > Unless ntpsec has fixed its NTP server (and I haven't heard if they > > have), it doesn't work with a Samba DC, so I would suggest only > > using Chrony. > As of 03/10/24, ntpsec (version 1.2.3+dfsg1-1) is fixed in Debian > Trixie; I can't speak for Fedora. >

I want to exchange information on how to get my MS-SNTP client working. Additionally, I am seeking guidance on how to program retrieving a valid 'Key Identifier'; that should be enough to get my MS-SNTP client working. Once accomplished, I can adequately test the ntp_signd code in NTPsec. Microsoft may have deprecated the implementation previously supported by Samba and third-party

Op 20-01-2025 om 11:52 schreef Rowland Penny via samba: > On Sun, 19 Jan 2025 17:51:54 +0100 > Peter Milesson via samba <samba at lists.samba.org> wrote: > >> >> >> On 19.01.2025 17:30, Sonic via samba wrote: >>> When I first did a Samba upgrade to 4.19.3 on Debian Bookworm back >>> in December of 2023 Chrony was working just fine for a natural

On Sat, 06 Jan 2024 13:06:48 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > On Sat Jan 6 03:34:43 2024 Rowland Penny via samba > <samba at lists.samba.org> wrote: > > > > 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.

On Sun, 19 Jan 2025 17:51:54 +0100 Peter Milesson via samba <samba at lists.samba.org> wrote: > > > > On 19.01.2025 17:30, Sonic via samba wrote: > > When I first did a Samba upgrade to 4.19.3 on Debian Bookworm back > > in December of 2023 Chrony was working just fine for a natural > > domain time sync to the DC - no special config or GPO necessary. So >

On Sat Jan 6 03:34:43 2024 Rowland Penny via samba <samba at lists.samba.org> wrote: > > 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

Hi there, In my experience NTP has been trouble lately with the NTPsec implementation. A few months back I decided to remove NTPsec and go with Chrony. These are my notes: http://samba.bigbird.es/doku.php?id=samba:install-chrony Hope it helps. On Oct 25, 2023 at 19:04 +0200, Ham <ham at kc0dxf.net>, wrote: > > Any ideas on what the problem is?

I was able to switch to Chony and verify that it is working. Clients are now getting time from the DC. Luis has good notes! On 10/25/23 12:06, Luis Peromarta via samba wrote: > Hi there, > > In my experience NTP has been trouble lately with the NTPsec implementation. > > A few months back I decided to remove NTPsec and go with Chrony. > > These are my notes: > >

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

On Fri Jan 5 03:23:48 2024 Peter Milesson via samba <samba at lists.samba.org> wrote: > > On 05.01.2024 1:28, Mark Foley via samba wrote: > > I've added a Windows 10 domain member to my Domain. I'm now following the > > procedure in https://wiki.samba.org/index.php/Time_Synchronisation#Configuring_Time_Synchronisation_on_a_Windows_Domain_Member. > > > >

> On 10/25/2023 11:16 AM PDT Rowland Penny via samba <samba at lists.samba.org> wrote: > > > On Wed, 25 Oct 2023 11:53:07 -0500 > Ham via samba <samba at lists.samba.org> wrote: > > > It appears that none of our windows clients are syncing their time > > with the samba DC.??? From what I can tell they are not able to get a > > response from the

On Wed, 25 Oct 2023 11:53:07 -0500 Ham via samba <samba at lists.samba.org> wrote: > It appears that none of our windows clients are syncing their time > with the samba DC.??? From what I can tell they are not able to get a > response from the DC.? For example, where the DC is named athena: > > >w32tm /monitor /computers:athena > > athena[10.10.1.10:123]

> On 10/25/2023 9:53 AM PDT Ham via samba <samba at lists.samba.org> wrote: > > > It appears that none of our windows clients are syncing their time with > the samba DC.??? From what I can tell they are not able to get a > response from the DC.? For example, where the DC is named athena: > > >w32tm /monitor /computers:athena > >

I haven't seen anyone mention this on the list, but found on the Debian changelog for ntpsec: ntpsec (1.2.3+dfsg1-1) unstable; urgency=low [...] - We think we have fixed ms-sntp Thanks to Jakob Haufe for testing. (Closes: 1033088) [...] -- Richard Laager<rlaager at debian.org> Sun, 10 Mar 2024 22:01:29 -0500 This version is for Debian Trixie; currently, no mention of

On Wed, 25 Oct 2023 11:10:57 -0700 (PDT) James Browning via samba <samba at lists.samba.org> wrote: > > On 10/25/2023 9:53 AM PDT Ham via samba <samba at lists.samba.org> > > wrote: > > > > > > It appears that none of our windows clients are syncing their time > > with the samba DC.??? From what I can tell they are not able to get > > a

On 20.01.2025 15:14, Sonic via samba wrote: > On Mon, Jan 20, 2025 at 5:53?AM Rowland Penny via samba < > samba at lists.samba.org> wrote: > >> I cannot get Chrony to work with MS-SNTP from a Windows client, now >> this could be a Samba problem.... >> > The reason I think it's a Samba issue is that it worked perfectly with > 4.19.3 but no longer works

On Wed, 25 Oct 2023 11:25:14 -0700 (PDT) James Browning via samba <samba at lists.samba.org> wrote: > > On 10/25/2023 11:16 AM PDT Rowland Penny via samba > > <samba at lists.samba.org> wrote: > > > > > > On Wed, 25 Oct 2023 11:53:07 -0500 > > Ham via samba <samba at lists.samba.org> wrote: > > > > > It appears that none of

On Sun, 2018-06-03 at 17:40 +0300, Alexei Rozenvaser via samba wrote: > By the way there is ntpsigndsocket option in chrony configuration > file. https://chrony.tuxfamily.org/doc/3.3/chrony.conf.html#ntpsigndsocket > Can you please look at > https://wiki.alpinelinux.org/wiki/Setting_up_a_samba-ad-dc and may be > https://chrony.tuxfamily.org/comparison.html ? Neat! While the