similar to: Sysvol gets corrupted permissions

Hello. I was able to solve the problem. The system was using the libwbclient library of the samba package. I just did the following: Yum install sssd-libwbclient Set this new library installed with default on the system: Alternatives --set libwbclient.so.0.12-64 /usr/lib64/sssd/modules/libwbclient.so.0.12.0 And restart the smbd and sssd daemons: Systemctl restart sssd smbd Now I can set the

I have two domain controller servers, with samba in version 4.18 On both DCs both the Sysvol share and the subdirectories (including GPOs) have the same permission: getfacl /usr/local/samba/var/lib/samba/sysvol # file: usr/local/samba/var/lib/samba/sysvol # owner: root # group: 3000000 user::rwx user:root:rwx user:3000000:rwx user:3000001:r-x user:3000002:rwx user:3000003:r-x group::rwx

OK - some more detail I have found in the meantime. I have compiled & ran listxattr, and I can 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/

First of all, thank you. Yes. I'm sure sssd is running 100%. The documentation of the link that passed me served as a basis to implement. I'll follow your advice and I'll ask you on the sssd user list. Even so, I hope someone else who went through the same score answers here. Thank you all. 2017-03-19 18:16 GMT-03:00 Rowland Penny via samba <samba at lists.samba.org>: >

HI, We have done something similar using inotify. On the DC1. we watch the "/usr/local/samba/var/locks/sysvol" folder and if there is any change, (add, modify or delete), we run "samba-tool ntacl sysvolreset" and we push those changes to other DCs using rsync. We have created a shell script that is put in rc.local so that this starts even if the server reboots. We chose

Can you tell me what are correct permissions to set at sysvol in order to work and how to solve that problem with 'Domain admins' uid ? I´m using samba 4.4.6 and i will upgrade to 4.4.10 but i´d like to correct this issue before. Thanks again Rowland. 2017-03-07 13:34 GMT-03:00 Rowland Penny via samba <samba at lists.samba.org>: > On Tue, 7 Mar 2017 13:16:23 -0300 > Edson

Hi, We have solved the problem and the command 'samba-tool ntacl sysvolreset' is working correctly again. We have been able to reset the SYSVOL permissions and the AD GPOs are working again. The problem is that if we have the audit options active in the smb.conf, that command stops working. We don't know why. If we temporarily remove them if it works. I know that we have an old

Hi, On Thu, 18 Jul 2019 at 14:27, Rowland penny via samba <samba at lists.samba.org> wrote: > > On 18/07/2019 14:11, Jonathan Hunter via samba wrote: > > For me, at least, "ntacl sysvolreset" is definitely broken and has > > been for the last few years. It's on my list of things I really need > > to fix as soon as possible, but I just haven't had

Thanks for the answer. But even removing the write list parameter, the problem persists. Excuse me. But the sssd service is working perfectly, and I see no reason to ask for help on the sssd user list. One important information is that when I apply the ACLs using the setfacl command the mapping is done and the permissions are applied. But when I use windows explorer the ACLs permissions are

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

On Tue, 7 Mar 2017 13:16:23 -0300 Edson Tadeu Almeida da Silveira <edson.tadeu at gmail.com> wrote: > Hi Rowland. > > But, samba automaticaly do this mapping. > > root at server:/usr/local/src/samba-4.4.10# id 'domain admins' > uid=3000008(DOMAIN\domain admins) gid=3000008(DOMAIN\domain admins) > groups=3000008(DOMAIN\domain admins) > > > Because of

Hello. Yes, it is possible. 2017-03-20 13:19 GMT-03:00 Moby <list at mobsternet.com>: > Thanks Edson, so the Samba member server will work fine even if we > increase the activedirectory domain functional level to 2016? > > Regards, > --Moby > > > On 3/19/2017 21:10, edson wrote: > > There is no problem if the samba server is a member server. But if it is >

On 10/12/2015 12:20 PM, Stefan Kania wrote: > Hello, > > when I check ACLs on my sysvol I got the following errors: > > root at DKHHDC1:~# samba-tool gpo aclcheck > ERROR(<type 'exceptions.KeyError'>): uncaught exception - 'No such > element' > File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", > line 175, in _run >

On Wed, 17 Jul 2019 at 17:58, Rowland penny via samba <samba at lists.samba.org> wrote: > > On 17/07/2019 17:43, Kris Lou via samba wrote: > > I had thought that the conventional wisdom was that ntacl sysvolreset > > should be mostly avoided once relative stability achieved and additional > > GPO's created. > > > >

Thanks for the answer. The path for the two DCs is correct yes, and yes I compiled it for the two DC servers like this: ./configure --with-systemd --prefix=/usr/local/samba --enable-fhs make up make install After the domain was created, sysvol was created here: /usr/local/samba/var/lib/samba/sysvol And the new DC also created sysvol in the same location. But why samba-tool ntacl sysvolreset

Hello! Any idea? Em 10-06-2016 14:29, Carlos A. P. Cunha escreveu: > Hello! > > I have two Dcs Samba 4 version 4.4.0, the DC 2 received rsync to DC 1, > ok this SYSVOL, but necessary execute "samba-tool ntacl sysvol reset", > for correct ids, but now is a one error this process: > > samba-tool ntacl sysvolreset > open: error=2 (No such file or directory) >

Hi Gabriel, I"ll answer to the lists email adress. Am 22.05.2015 um 16:54 schrieb Gabriel Franca: > follows the output of the command: > > attr -l / var / lib / samba / sysvol > Attribute "SGI_ACL_FILE" has a 124 byte value for / var / lib / samba > / sysvol > Attribute "SGI_ACL_DEFAULT" has a 124 byte value for / var / lib / > samba / sysvol

On 6/14/2016 9:53 AM, Carlos A. P. Cunha wrote: > Hello! > > Any idea? > > > Em 11-06-2016 16:13, Carlos A. P. Cunha escreveu: >> >> Hello! >> >> Any idea? >> >> >> Em 10-06-2016 14:29, Carlos A. P. Cunha escreveu: >>> Hello! >>> >>> I have two Dcs Samba 4 version 4.4.0, the DC 2 received rsync to DC

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 13.10.2015 um 11:20 schrieb Stefan Kania: > Am 12.10.2015 um 18:47 schrieb James: >> On 10/12/2015 12:20 PM, Stefan Kania wrote: >>> Hello, >>> >>> when I check ACLs on my sysvol I got the following errors: >>> >>> root at DKHHDC1:~# samba-tool gpo aclcheck ERROR(<type >>>

Hello! I have two Dcs Samba 4 version 4.4.0, the DC 2 received rsync to DC 1, ok this SYSVOL, but necessary execute "samba-tool ntacl sysvol reset", for correct ids, but now is a one error this process: samba-tool ntacl sysvolreset open: error=2 (No such file or directory) ERROR(runtime): uncaught exception - (-1073741823, 'Undetermined error') File