similar to: Member join to Active Directory -> DNS-Update fails

Am 27.05.2024 17:46, schrieb Rowland Penny via samba: > On Mon, 27 May 2024 17:27:30 +0200 > Bestattungen Vitt - Thomas Reitelbach via samba <samba at lists.samba.org> > wrote: > >> Am 27.05.2024 16:25, schrieb Rowland Penny via samba: >> > On Mon, 27 May 2024 15:57:52 +0200 >> > Bestattungen Vitt - Thomas Reitelbach via samba >> > <samba at

Am 28.05.2024 07:51, schrieb Christian Naumer via samba: > Am 28.05.24 um 07:34 schrieb Bestattungen Vitt - Thomas Reitelbach via > samba: >> >> Christian Naumer said, I can get Nextcloud to work without this >> insecure parameter - I'll have to figure out how I could acceppt a >> self-signed certificate on the side of apache2/php-ldap module. > > I

Am 27.05.2024 16:25, schrieb Rowland Penny via samba: > On Mon, 27 May 2024 15:57:52 +0200 > Bestattungen Vitt - Thomas Reitelbach via samba <samba at lists.samba.org> > wrote: > >> Hello Samba Team, >> >> I hope someone with more expertise than me can englighten me to the >> following "problem": >> >> I'm on my way to

Hello Samba Team, I hope someone with more expertise than me can englighten me to the following "problem": I'm on my way to implement Nextcloud LDAP Authentication against my existing Samba Active Directory via the LDAP Auth Plugin in Nextcloud. I have had trouble with the configuration of the Auth-Plugin in Nextcloud because it could not bind to the ldap directory. After some

On Mon, 27 May 2024 17:27:30 +0200 Bestattungen Vitt - Thomas Reitelbach via samba <samba at lists.samba.org> wrote: > Am 27.05.2024 16:25, schrieb Rowland Penny via samba: > > On Mon, 27 May 2024 15:57:52 +0200 > > Bestattungen Vitt - Thomas Reitelbach via samba > > <samba at lists.samba.org> wrote: > > > >> Hello Samba Team, > >> >

Am 28.05.24 um 07:34 schrieb Bestattungen Vitt - Thomas Reitelbach via samba: > > Christian Naumer said, I can get Nextcloud to work without this insecure > parameter - I'll have to figure out how I could acceppt a self-signed > certificate on the side of apache2/php-ldap module. I checked our installation and found this in the Nextcloud Doku

Hello Thomas, we've done the exact same thing: we have a few nextcloud instances bound to Samba (now 4.20, but 4.19 worked too). You HAVE to use "ldaps://<FQDN>" in the "Host" field and "636" in the "Port" field. For the certificates issues: either you create a CA, create the samba certificates and add this CA to the trusted certificate

On Mon, 27 May 2024 15:57:52 +0200 Bestattungen Vitt - Thomas Reitelbach via samba <samba at lists.samba.org> wrote: > Hello Samba Team, > > I hope someone with more expertise than me can englighten me to the > following "problem": > > I'm on my way to implement Nextcloud LDAP Authentication against my > existing Samba Active Directory via the LDAP

Hi, there is a suitable HowTo on how to create your own CA at: https://checkmk.com/de/blog/how-become-your-own-certificate-authority So long Thom Am 28.05.24 um 09:20 schrieb Matthias K?hne | Ellerhold Aktiengesellschaft via samba: > Hello Thomas, > > we've done the exact same thing: we have a few nextcloud instances bound > to Samba (now 4.20, but 4.19 worked too). >

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 20 January 2025 15:18 Luis Peromarta wrote: > > I hope to be able to do the same kind of tests, > On 20 Jan 2025 at 15:10 +0000, Peter Milesson <miles at atmos.eu>, wrote: > > > > I have tested with Windows 7 Pro (SP1), Windows 10 Pro (22H2), and > > Windows 11 Pro (24H2). All those clients report CMOS clock as time > > source. I also suspect that

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 >

I hope to be able to do the same kind of tests, On 20 Jan 2025 at 15:10 +0000, Peter Milesson <miles at atmos.eu>, wrote: > > I have tested with Windows 7 Pro (SP1), Windows 10 Pro (22H2), and > Windows 11 Pro (24H2). All those clients report CMOS clock as time > source. I also suspect that something broke in Samba since I posted > about this problem on 9 August 2023. Then I

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 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 after seeing this > thread I decided to see what was different about my configuration that > allowed it to work so seamlessly and I was

FWIW, I looked at the settings in our domain (all of which I did myself). I used to explicitly set up ntp time sources in our network for all windows workstations before, and I continued to provide these after conversion from nt4-style domain to samba AD-DC. The NTP records are provided by DHCP, and are configured in the GPO, both with regional differences (choosing the local NTP servers within

My tests: -Boot a backed up ?new? VM with chrony 4.3 and samba 4.19 installed, joined a new Win 10 machine, time syncs OK with Type: NT5DS. -Updated DC samba to 4.21.3 without removing the Windows machine from domain. Time syncs OK with NT5DS. -Leave domain, try to w32tm /monitor -> error can?t reach DCs (expected) -Join domain again: time syncs OK with NT5DS. I can?t reproduce. Can we make

> 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 > >

On Mon, Jan 20, 2025 at 2:19?PM spindles seven via samba <samba at lists.samba.org> wrote: > > On 20 January 2025 15:18 Luis Peromarta wrote: > > > > I hope to be able to do the same kind of tests, > > On 20 Jan 2025 at 15:10 +0000, Peter Milesson <miles at atmos.eu>, wrote: > > > > > > I have tested with Windows 7 Pro (SP1), Windows 10 Pro

Hi folks, I have been spending the better part of the day, trying to get time synchronization to a Samba AD DC (Debian Bookworm 12.1) to work. Debian Bookworm has recently replaced ntp with ntpsec, and time synchronization stopped working. I have logged the behavior, and Windows 10 clients first send a Windows 2000! compatible request, and ntpsec chokes on it, and does not respond. The