Hi, I found the source of my problem with set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_OWNER (I hope). The problem is dut to winbind. In my ldap tree, I have uid and gid. Why samba 4 don't use theses informations ? In attached file : output of classic-upgrade (debug level 5) I don't want to use winbind. I just want to use pam_ldap or nslcd for have unix information from samba ldb regards St?phane ----------------------------------- St?phane PURNELLE Admin. Syst?mes et R?seaux Service Informatique Corman S.A. Tel : 00 32 (0)87/342467
Hi, I found the source of my problem with set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_OWNER (I hope). The problem is dut to winbind. In my ldap tree, I have uid and gid. Why samba 4 don't use theses informations ? log file available I don't want to use winbind. I just want to use pam_ldap or nslcd for have unix information from samba ldb regards St?phane ----------------------------------- St?phane PURNELLE Admin. Syst?mes et R?seaux Service Informatique Corman S.A. Tel : 00 32 (0)87/342467
Maybe Matching Threads
- Error on classicupgrade - Unable to get id for sid
- Classicupgrade "set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_OWNER"
- Samba classicupgrade problem
- samba4, classicupgrade: set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_OWNER
- samba-tool ntacl sysvolreset - NT_STATUS_BUFFER_TOO_SMALL