similar to: Timestamps on -d 10 output from samba-tool

Hi all, I have a Samba 4.0.0 domain running on a Gentoo box with a 3.7.0 kernel. I have added 'winbind' to the passwd and group lines in /etc/nsswitch.conf wbinfo -t returns immediately saying trust checking succeeded. wbinfo -g returns immediately with a list of groups wbinfo -u takes a long time to return a list of users # time wbinfo -u | wc -l 336 real 0m4.211s user 0m0.000s

Hi all, Some (then all) of our workstations were complaining about incorrect ACLs on GPOs and were unable to read the gpt.ini to apply the GPOs. So I did a sysvolcheck and sure enough I'd lost the ACLs when I moved our sysvol share to a new location on the server (whoops, mea culpa). I ran a sysvolreset which took a long time to return (some 5 minutes, please see my post on slow winbind

On 18/07/2019 14:11, Jonathan Hunter via samba wrote: > 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 >>>

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

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, after adding a new GPO the ntacl sysvolcheck fails and i want wo repair with ntacl sysvolreset.... biut this fails aslo in the end with: connect_acl_xattr: setting 'inherit acls = true' 'dos filemode = true' and 'force unknown acl user = true' for service sysvol open: error=2 (No such file or directory) ERROR(runtime): uncaught exception - (-1073741823,

On Mon, 13 Nov 2017 09:59:23 +0100 Sina Owolabi via samba <samba at lists.samba.org> wrote: > Hi List! > > I am working my way through getting familiar with samba and I have two > domain controllers now with an additional samba file server. > The servers are CentOS 7.4.1708; > the domain controllers are built from source with samba-4.7.1; > and the file server,

> OK, make sure that the two idmap.ldb files match and then run > 'samba-tool ntacl sysvolreset' on both machines and see if this cured > this problem. I did: root at dc1:~$ service sernet-samba-ad stop root at dc2:~$ service sernet-samba-ad stop root at dc2:~$ mv /var/lib/samba/private/idmap.ldb /root/idmap.ldb.bak root at dc1:~$ scp /var/lib/samba/private/idmap.ldb

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

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

> On Tue, 11 Sep 2018 01:16:16 +0100 > niya via samba <samba at lists.samba.org <https://lists.samba.org/mailman/listinfo/samba>> wrote: > > >/hi everyone />//>/installed and joined a second dc following the instructions at />/https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory > />/both version are 4.8.2 />/when i try

On my small, one DC AD setup, where I just followed the wiki and did not (!) make any other changes except for working on the AD through the RSAT, I ran samba-tool ntacl sysvolcheck and got the following output: --------------------snip-------------------- ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: DB ACL on GPO directory

Hi, I got same problem describe in [1] python error end with File "/usr/lib/python2.7/site-packages/samba/ntacls.py", line 162, in setntacl so I edited ntacls.py [2] and one line before the error (line 161 in this case) I add print(file) and I found default domain policie {31B2F340-016D-11D2-945F-00C04FB984F9} was gone from file system (the error is pretty clear "no such file

Hi all, Is it a necessity to use the winbind nss module? I have run a few tests and having it enabled creates a massive bottleneck. It's not nss_winbind itself that is the bottleneck but something in the background (I'm guessing uid/rid->username code). If I disable winbind in nsswitch.conf what impact will it have? Will the system continue to work? eg: #nss_winbind enabled on

Hi I'm with this problem? Version: Samba 4.3 (4.2 upgrade) S.O .: Ubuntu 4.14 samba-tool ntacl sysvolreset open: error=2 (No such file or directory) ERROR(runtime): uncaught exception - (-1073741823, 'Undetermined error') File "/opt/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", line 175, in _run return self.run(*args, **kwargs) File

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 all, We're seeing the following: root at dc3:~# samba-tool ntacl sysvolcheck rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[netlogon]" Processing section "[sysvol]" ERROR(<type 'exceptions.TypeError'>): uncaught exception - (61, 'No data available') File

W dniu 19.04.2024 o?11:00, Kees van Vloten via samba pisze: > > On 19-04-2024 10:33, Jaros?aw K?opotek - INTERDUO via samba wrote: >> W dniu 19.04.2024 o?09:59, Jaros?aw K?opotek - INTERDUO via samba pisze: >>> W dniu 18.04.2024 o?18:11, David Mulder via samba pisze: >>>> On 4/18/24 1:03 AM, Jaros?aw K?opotek - INTERDUO via samba wrote: >>>>> Hi all,

Hi, After making progress with my scripts for software installation (thanks, Rowland!) I am on a bit of a mission to get things working again. I found that permissions on my sysvol share were somehow incorrect (group ownership was root, etc.) so I ran 'samba-tool ntacl sysvolreset'.. however this now fails with the following error. (I'm on Samba 4.5.0) user at dc2:~ $ sudo

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