search for: workingfile

...an now see a difference between a working and a broken file: me at dc2:~/download $ sudo ./listxattr /usr/local/samba/var/locks/sysvol/ mydomain.org/brokenfile.txt user.DOSATTRIB: 0x20 system.posix_acl_access: me at dc2:~/download $ sudo ./listxattr /usr/local/samba/var/locks/sysvol/ mydomain.org/workingfile.txt user.DOSATTRIB: 0x20 system.posix_acl_access: security.NTACL: This then led me to check what things look like from Windows, and to look at the NTACL from there, seeing as 'listxattr' wasn't showing me much: C:\Users\me>cacls \\dc2\sysvol\mydomain.org\brokenfile.txt /S \\dc2\sys...

Hi, I have been having problems with GPOs, sysvol, etc. for some time now, and have found a workaround but I wondered if any of the samba devs were interested in investigating this. Basically, the problems manifest themselves as access errors, along the lines of unable to read files, error messages such as 'The data area passed to a system call is too small' and so on - which means that

...a broken file: > > me at dc2:~/download $ > sudo ./listxattr /usr/local/samba/var/locks/sysvol/ > mydomain.org/brokenfile.txt user.DOSATTRIB: 0x20 > system.posix_acl_access: > > me at dc2:~/download $ > sudo ./listxattr /usr/local/samba/var/locks/sysvol/ > mydomain.org/workingfile.txt user.DOSATTRIB: 0x20 > system.posix_acl_access: > security.NTACL: Are you sure your sync method is working ? I ask this because the sysvol ACLs are stored in 'security.NTACL' and you don't have this on the non working DC > > This then led me to check what things look...