search for: nss_nested_group

Hello guys I need some lights to migrate a Winbind/Samba share to a new AD. My scenario is: I have an old AD running on a Debian 9 and Samba 4.5.16 with many replication issues. Then I decided to create a new one from the scratch using Debian 10 and Samba 4.12.2 (and everything is working perfectly). I have migrated all the accounts/machines/etc from old to new domain without any problem. Both the

...file. See nslcd.conf(5) # for details. # The user and group nslcd should run as. uid nslcd gid nslcd # The location at which the LDAP server(s) should be reachable. uri???????????? ldap://dc1.samdom.example.com/ base??????????? dc=samdom,dc=example,dc=com pagesize??????? 1000 referrals?????? off nss_nested_groups yes # Kerberos authentication to AD sasl_mech?????? GSSAPI sasl_realm????? SAMDOM.EXAMPLE.COM krb5_ccname???? /tmp/nslcd.tkt # Filters. Disable, if your: filter? passwd? (objectClass=user) filter? group?? (objectClass=group) # Attribute mappings map???? passwd? uid??????????????? sAMAccountName...

...he user and group nslcd should run as. > uid nslcd > gid nslcd > > # The location at which the LDAP server(s) should be reachable. > uri ldap://dc1.samdom.example.com/ > base dc=samdom,dc=example,dc=com > pagesize 1000 > referrals off > nss_nested_groups yes > > # Kerberos authentication to AD > sasl_mech GSSAPI > sasl_realm SAMDOM.EXAMPLE.COM > krb5_ccname /tmp/nslcd.tkt > > # Filters. Disable, if your: > filter passwd (objectClass=user) > filter group (objectClass=group) > > # Attribute mappin...