similar to: samba-tool ntacl sysvolreset - NT_STATUS_BUFFER_TOO_SMALL

OK, I've traced this a little further on now. I think I have followed the trail via the following items that call or refer to each other in turn: - python samba-tool ntacl sysvolreset - source3/smbd/pysmbd.c: SMB_VFS_FSET_NT_ACL( fsp, security_info_sent, sd); - source3/include/vfs_macros.h:#define SMB_VFS_FSET_NT_ACL smb_vfs_call_fset_nt_acl - source3/smbd/vfs.c:NTSTATUS

Hi, I'm trying to setup a domain with two DCs based on 4.0.3. Following some hint, I wanna use glusterfs for the sysvol. Glusterfs it runs nicely. I can set acls on both machines using setfacl and the other one lists them almost immediately with getfacl. But running "samba-tool ntacl sysvolreset is failing badly giving the following error. In a later attempt, without significant

Dear all, I've upgraded my Samba 4.1 to Samba 4.2, compiled from source (CentOS 7). Now, if I run samba-tool ntacl sysvolreset, I get this error: set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_ACCESS_DENIED. Existing GPOs works fine, but if I create a new one, I get ACCESS DENIED when I click Apply. Does anyone have any suggestions? Thanks, Paul -- -----BEGIN PGP PUBLIC KEY BLOCK-----

Hi, i have a problem upgrading an old samba 3.5.x to 4.0.9. The upgrade ends with: Setting password for administrator Administrator password has been set to password of user 'root' set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_OWNER. ERROR(runtime): uncaught exception - (-1073741734, 'NT_STATUS_INVALID_OWNER') File

Hello, I am stuck with a error when setting password for a couple of specific users. This error makes impossible to set the password for the affected users. In Windows I get an operation error but the samba-tool output is more informative: samba-tool user setpassword user2 --newpassword= New Password: ndr_pull_error(11): Pull bytes 2 (../librpc/ndr/ndr_basic.c:103) ERROR: Failed to set

Hi, I am finally revisiting my sysvol share (GPOs haven't been working for me for quite some time) and trying to get permissions sorted properly on it. For many years, "samba-tool ntacl sysvolreset" has always failed for me with errors that I have been unable to solve. Previously I have used guidance from Louis and got things working, but my sysvol is currently in a broken state.

i'm running (well trying to run) samba3a20-4 from debian with sam backend = ldapsam_nua:ldap://localhost/ when i try to log in I get a message saying that the roaming profile has the wrong permissions. There is no profile in place for this user... it should be created from the netlogon share (which was copied to netlogon via the system control panel with "everybody" given permission

Hi, I have a problem during the classicupgrade. The problem was discussed in march on this list, but there seems to be nosolution. Can anyone help? ... Setting password for administrator Administrator password has been set to password of user 'root' idmapping sid_to_xid failed for id[0]=S-1-5-32-544: NT_STATUS_NONE_MAPPED set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_OWNER.

Hello all, I am looking to setup a Samba AD on my NAS. I am currently using the latest version of NAS4Free which has Samba bundled into it already. However, I am getting a very nasty error when I go in to setup the samba service: Initializing... Looking up IPv4 addresses Looking up IPv6 addresses No IPv6 address will be assigned Setting up share.ldb Setting up secrets.ldb Setting up the

Following the wiki replication guide precisely I got to this step. [root at smb4-2 ~ (master)]# rsync -XAavz --delete-after smb4-1.brockley.harte-lyne.ca:/var/db/samba4/sysvol/ /var/db/samba4/sysvol/ receiving file list ... done ./ brockley.harte-lyne.ca/ . . . brockley.harte-lyne.ca/scripts/ sent 142 bytes received 1,683 bytes 3,650.00 bytes/sec total size is 182 speedup is 0.10 [root at

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

piggybacking on the "Syncing Sysvol" thread ... I had thought that the conventional wisdom was that ntacl sysvolreset should be mostly avoided once relative stability achieved and additional GPO's created. https://wiki.samba.org/index.php/Sysvolreset Has this changed recently? Kris Lou klou at themusiclink.net

Hi, In reading this list I see a lot of talk about samba-tool ntacl sysvolreset actually breaking things. Given the above How do I properly configure a 2nd AD DC or setup sysvol replication? For instance If I were to follow https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory In the Built-in Groups GID Mappings section the last thing it says to do is run samba-tool

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

On Thu, 6 Jul 2017 12:17:42 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Thu, 6 Jul 2017 05:27:13 -0500 > Andrew Walker via samba <samba at lists.samba.org> wrote: > > > I'm sorry. I probably should have linked their samba fork: > > https://github.com/freenas/samba You can look at the commits from > > around the time period of

Hello, We're having a problem with "Samba 4" joined to a "Server 2008 R2" domain (at "Server 2008" functional level across the forest). The interesting thing is that this only affects a single user - all other accounts work without problems. When accessing our main server using that account, "smbd" always reports "can't parse the PAC:

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. > > > >

Samba 4.4.2 I was doing some maintenance work and I noticed that sysvolcheck gave some error. I ran "samba-tool ntacl sysvolreset". Running sysvolcheck again still gives errors. I tried with several sysvol backups and the result is always the same. The affected policies are always "Default Domain Policy" and "Default Domain Controllers Policy". These policies

Mandi! Rowland Penny via samba In chel di` si favelave... > The error you are getting is usually caused by adding GPOs to the first > DC and then NOT copying them to the second DC before running > 'sysvolreset'. The GPOs are also stored in AD, 'sysvolreset' reads AD > to find where the GPOs are supposed to be, but if it cannot find any, > it errors out.

Hi Rowland I removed the winbind lines, and added the 'idmap_ldb:use rfc2307 = yes' line to the second DC, and rebooted the servers, but the error does not go away. First DC: [global] dns forwarder = 8.8.8.8 netbios name = TESTBOX realm = SAMDOM.TESTING.COM server role = active directory domain controller workgroup = SAMDOM idmap_ldb:use