similar to: pam_winbind vs. pam_ldap ?

Greetings, All! I'm using Samba 3.6 and OpenLDAP currently. The core configuration has been done eons ago, and I'm not quite sure it is actual any more. I see a number of PAM-related errors every time the system boot up. One concerning me is Jan 28 02:31:21 daemon1 perl: pam_ldap: error trying to bind as user "uid=root,ou=Users,dc=darkdragon,dc=lan" (Invalid credentials) Is this

On Fri, 9 Jun 2023 00:47:07 +0300 Andrey Repin via samba <samba at lists.samba.org> wrote: > Greetings, Rowland Penny via samba! > > > > > On 08/06/2023 13:53, Andrey Repin via samba wrote: > >> Hello Rowland Penny, > >> > Thursday, June 8, 2023, 2:10:39 PM, you wrote: > >> > > >> On 08/06/2023 11:41, Andrey Repin via samba

Greetings, Rowland Penny via samba! > On 08/06/2023 13:53, Andrey Repin via samba wrote: >> Hello Rowland Penny, >> > Thursday, June 8, 2023, 2:10:39 PM, you wrote: >> > > >> On 08/06/2023 11:41, Andrey Repin via samba wrote: >>>> Greetings, All! >>>>> I've added a new DC to the working AD, transferred FSMO roles (checked, all 7

On Tue, 7 Nov 2023 20:00:40 +0300 Andrey Repin via samba <samba at lists.samba.org> wrote: > Greetings, Rowland Penny via samba! > > > OK, I give in, why have 4 emails from Andrey Repin, that were > > apparently sent in May & June of this year, just appeared in my mail > > client ? > > Don't worry, your sanity is not affected. My mail provider had

On 08/06/2023 13:53, Andrey Repin via samba wrote: > Hello Rowland Penny, > > Thursday, June 8, 2023, 2:10:39 PM, you wrote: > > > >> On 08/06/2023 11:41, Andrey Repin via samba wrote: >>> Greetings, All! >>>> I've added a new DC to the working AD, transferred FSMO roles (checked, all 7 >>> are ok') and (supposedly) correctly

Greetings, All! I've added a new DC to the working AD, transferred FSMO roles (checked, all 7 are ok') and (supposedly) correctly demoted the old DC. SchemaMasterRole owner: CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN= InfrastructureMasterRole owner: CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=S RidAllocationMasterRole owner: CN=NTDS

Greetings, Rowland Penny via samba! > OK, I give in, why have 4 emails from Andrey Repin, that were > apparently sent in May & June of this year, just appeared in my mail > client ? Don't worry, your sanity is not affected. My mail provider had changed submission policy without a sufficient notification, causing my transit mail server to block mail queue since last August.

Greetings, All! I've added a new DC to the working AD, transferred FSMO roles (checked, all 7 are ok') and (supposedly) correctly demoted the old DC. SchemaMasterRole owner: CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN= InfrastructureMasterRole owner: CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=S RidAllocationMasterRole owner: CN=NTDS

Greetings, All! I've added a new DC to the working AD, transferred FSMO roles (checked, all 7 are ok') and (supposedly) correctly demoted the old DC. SchemaMasterRole owner: CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN= InfrastructureMasterRole owner: CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=S RidAllocationMasterRole owner: CN=NTDS

Hello, I think the configuration changed in 4.6. see here: https://wiki.samba.org/index.php/Idmap_config_ad Regards > Am 18.02.2018 um 00:00 schrieb Andrey Repin via samba <samba at lists.samba.org>: > > Greetings, All! > > I'm stumbled upon an event I can't understand. Rolled out a new Ubuntu 17.10 > box in preparation for eventual 18.04 launch and… it just

Greetings, All! I'm stumbled upon an event I can't understand. Rolled out a new Ubuntu 17.10 box in preparation for eventual 18.04 launch and… it just does not fly. Here's a brief and apparent summary of the problem: $ smbd -V; getent passwd anrdaemon Version 4.3.11-Ubuntu (14.04, 16.04) anrdaemon:*:10000:10001:Andrey Repin,,,,umask=0027:/home/anrdaemon:/bin/bash Version

On Sun, 18 Feb 2018 02:00:35 +0300 Andrey Repin via samba <samba at lists.samba.org> wrote: > Greetings, All! > > I'm stumbled upon an event I can't understand. Rolled out a new > Ubuntu 17.10 box in preparation for eventual 18.04 launch and… it > just does not fly. > > Here's a brief and apparent summary of the problem: > > $ smbd -V; getent passwd

Hello Andrew Bartlett, Friday, June 9, 2023, 11:25:01 PM, you wrote: > On Thu, 2023-06-08 at 13:41 +0300, Andrey Repin via samba wrote: >> Greetings, All! >> >> I've added a new DC to the working AD, transferred FSMO roles >> (checked, all 7 >> are ok') and (supposedly) correctly demoted the old DC. >> >> SchemaMasterRole owner: CN=NTDS

On Tue, 7 Nov 2023 21:52:56 +0300 Andrey Repin via samba <samba at lists.samba.org> wrote: > Greetings, Rowland Penny via samba! > > > I would remove these from the DC smb.conf, they are either defauts, > > not required or flat out doing nothing on a DC: > > > > auto services = homes > > client ldap sasl

Greetings, Rowland Penny via samba! > I would remove these from the DC smb.conf, they are either defauts, not > required or flat out doing nothing on a DC: > > auto services = homes > client ldap sasl wrapping = sign > tls enabled = Yes Without "tls enabled" ldaps:// access does not work. > winbind

LP On Nov 7, 2023 at 18:06 +0100, Andrey Repin via samba <samba at lists.samba.org>, wrote: > > > AD DC configuration: > > # Global parameters > [global] > auto services = homes > client ldap sasl wrapping = sign > dns forwarder = 192.168.1.12 > dos charset = CP866 > logging = systemd > log level = 1 > netbios name = DC2 > panic action =

Hello Rowland Penny, Friday, June 9, 2023, 8:51:25 PM, you wrote: > On 09/06/2023 18:11, Andrey Repin via samba wrote: >> Greetings, Rowland Penny via samba! >>> OK, you have these lines on the DC: >>> winbind nss info = rfc2307 >>> winbind use default domain = Yes >>> idmap config darkdragon : unix_nss_info = yes

On 09/06/2023 18:11, Andrey Repin via samba wrote: > Greetings, Rowland Penny via samba! >> OK, you have these lines on the DC: > >> winbind nss info = rfc2307 >> winbind use default domain = Yes >> idmap config darkdragon : unix_nss_info = yes >> idmap config darkdragon : unix_primary_group = yes >>

O, try the following.   Test this first. ldd /usr/sbin/hfaxd  if you getting libpam.so..  something, then hylafax is compiled with pam support.   Next,   apt-get install libpam-ldap   ( just to be sure, i do believe you have installed it already )   create the file :  /etc/pam.d/hylafax Add :   auth         required       pam_ldap.so account   required       pam_ldap.so

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, I posted this also on hylafax list - maybe here is someone with a hint. System: Debian Jessie, Hylafax-Server 6.0.6, pam 1.1.8, libpam-ldapd 0.9.4, nslcd 0.9.4 (all actual debian packets from stable), sernet-samba-*-4.2.7-8 After a switch from OpenLDAP to a Samba 4.2 based LDAP Server, I cannot auth users anymore in Hylafax, everything else