similar to: ntpsec

Displaying 20 results from an estimated 1000 matches similar to: "ntpsec"

2025 Jan 20
2
Time synchronization problem. Chrony, ntp
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
2024 Sep 19
2
The care and feeding of the signing socket; also NTPsec
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
2024 Sep 20
1
The care and feeding of the signing socket; also NTPsec
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. >
2025 Jan 20
2
Time synchronization problem. Chrony, ntp
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 >
2025 Jan 21
1
The failure of that guy from NTPsec getting an RID / Key Identifier
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
2017 Feb 08
0
Sieve LDA Errors (Improper Saving?)
Op 2/7/2017 om 5:04 AM schreef Richard Laager: > I'm getting lots of errors like this (possibly on every message delivery): > > imap2 dovecot: lmtp(rlaager at wiktel.com): Error: OU02K+gQmFhUAwAAVtfydQ > : sieve: binary save: failed to create temporary file: > open(/var/lib/dovecot/sieve/junk-mail.svbin.ima > p2.852.) failed: Permission denied (euid=500(vmail) egid=500(vmail)
2016 Mar 08
2
Dsync Header Hashing
On 03/04/2016 08:52 AM, Timo Sirainen wrote: > On 04 Mar 2016, at 07:47, Richard Laager <rlaager at wiktel.com> wrote: >> Is there any way to disable the header hashing in dsync? ... > Does the attached patch happen to work? Compiles, but untested for now. It works with one more change on top of your patch: diff --git a/src/doveadm/dsync/dsync-mailbox-export.c
2024 Sep 19
1
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
2016 Apr 12
1
Dsync Header Hashing
We've completed our migration to Dovecot (yay!), so this isn't critical for me any more. But this change might still be a useful addition to Dovecot. It doesn't create any non-standard behavior (like my patch for non-atom flags). On 03/07/2016 11:16 PM, Richard Laager wrote: > On 03/04/2016 08:52 AM, Timo Sirainen wrote: >> On 04 Mar 2016, at 07:47, Richard Laager
2024 Sep 19
1
The care and feeding of the signing socket; also NTPsec
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 that adding a line to start signd appeared to have broken everything else. I have attached a list of most of the steps I
2023 Oct 25
1
DC Time Problems
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
2023 Oct 25
1
DC Time Problems
> 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 > >
2017 Feb 07
2
Sieve LDA Errors (Improper Saving?)
I'm getting lots of errors like this (possibly on every message delivery): imap2 dovecot: lmtp(rlaager at wiktel.com): Error: OU02K+gQmFhUAwAAVtfydQ : sieve: binary save: failed to create temporary file: open(/var/lib/dovecot/sieve/junk-mail.svbin.ima p2.852.) failed: Permission denied (euid=500(vmail) egid=500(vmail) missing +w perm: /var/lib/dovecot/ sieve, dir owned by 0:0 mode=0755)
2025 Jan 20
1
Time synchronization problem. Chrony, ntp
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
2023 Oct 25
2
DC Time Problems
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
2018 Jun 04
0
chrony configuration for secondary samba DC
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
2025 Jan 21
1
The failure of that guy from NTPsec getting an RID / Key Identifier
On 22/01/25 02:59, James Browning via samba wrote: > > Attached is a packet capture from: > `tcpdump -i lo "udp port 123" -w mssntp.pcap` > It seems not to be attached. Douglas
2025 Jan 22
1
The failure of that guy from NTPsec getting an RID / Key Identifier
On Wed, 22 Jan 2025 12:48:36 +1300 Douglas Bagnall via samba <samba at lists.samba.org> wrote: > On 22/01/25 02:59, James Browning via samba wrote: > > > > > Attached is a packet capture from: > > `tcpdump -i lo "udp port 123" -w mssntp.pcap` > > > > It seems not to be attached. > > Douglas > > That is because this list
2025 Jan 20
1
Time synchronization problem. Chrony, ntp
On Mon, 20 Jan 2025 09:38:50 -0500 Jeffrey Walton via samba <samba at lists.samba.org> wrote: > On Sat, Jan 18, 2025 at 3:49?AM Programnet via samba > <samba at lists.samba.org> wrote: > > > > I noticed a problem with time synchronization on all Windows > > endpoints. I am using Samba 4.21.3 and Chrony 4.3-2. > > > > When I run the following command
2024 Jan 06
1
Joining Windows 10 Domain Member to Samba AD/DC
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.