similar to: Windows ACLs

On 2017-04-23 17:19, Henry via samba wrote: > On 2017-04-23 17:01, Rowland Penny wrote: >> On Sun, 23 Apr 2017 14:07:44 +1000 >> Henry via samba <samba at lists.samba.org> wrote: >> >>> Following: >>> >>> https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs >>> >>> In windows: >>> >>> I

On 2017-04-23 17:01, Rowland Penny wrote: > On Sun, 23 Apr 2017 14:07:44 +1000 > Henry via samba <samba at lists.samba.org> wrote: > >> Following: >> >> https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs >> >> In windows: >> >> I can set permissions under the "Share Permissions" tab. >> >> I am

On 2017-04-24 01:44, Rowland Penny wrote: > On Sun, 23 Apr 2017 20:53:39 +1000 > Henry via samba <samba at lists.samba.org> wrote: > >> root at aphrodite:~# getfacl -d /srv/samba/data/Testing >> getfacl: Removing leading '/' from absolute path names >> # file: srv/samba/data/Testing >> # owner: root >> # group: domain\040admins >>

On Sun, 23 Apr 2017 20:53:39 +1000 Henry via samba <samba at lists.samba.org> wrote: > root at aphrodite:~# getfacl -d /srv/samba/data/Testing > getfacl: Removing leading '/' from absolute path names > # file: srv/samba/data/Testing > # owner: root > # group: domain\040admins > > However in Windows I am still unable to edit the "Security" >

Hi folks, It seems that the setting acl_xattr:ignore system acls = yes reduces Windows compatibility when defined for a share. In all attempts I have used Windows tools (except editing smb.conf) Assume there is a share, where the files and folders in the share root should at least be readable by anybody having access to the share. For the sake of simplicity the following permissions apply on

Hey all, I decided to use the default ranges in the smb.conf of my member server, so I changed my smb.conf and it looks like that: ================================================== [global] netbios name = MEMBERSRV workgroup = MYDOM security = ADS realm = MYDOM.EXAMPLE.COM encrypt passwords = yes idmap config MYDOM:backend = ad idmap

Does you filesystem support extended attributes? What does "|getfattr -n security.NTACL |filename" return?|| On 30.01.2024 16:13, Peter Milesson wrote: > Hi folks, > > It seems that the setting acl_xattr:ignore system acls = yes reduces > Windows compatibility when defined for a share. In all attempts I have > used Windows tools (except editing smb.conf) > > Assume

Hi, i have setup an ad dc with samba 4.8, and then rigorously followed wiki tutorial at : https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs However, when following the last part (File System ACLs in the Back End), I don't get the expected results : [root at mydc ~]# getfattr -d /srv/samba/Demo/ doesn't yield anything and getfacl /srv/samba/Demo/ getfacl : suppression

Hello. I've got a working SAMBA AD server. I'm able to join both Linux (winbind) and Windows clients. I have also joined an NAS that hosts some shares/folders to be used by multiple machines (Linux and Windows 10). On my Linux host I'm accessing the NAS via NFS mount, while on my Windows machine obviously I'm using SMB. I'm using the ad ID mapping backend with uId and gId that

Hi everyone, since i upgraded from 4.10.2 to 4.10.4 i can't write into subdirectories of a share anymore. This worked perfectly fine before i upgraded and also works again if i downgrade.? I think either something is fishy with the 'filename_convert_internal' function of ".../source3/smbd/filename.c" or my configuration needs to be adjusted for 4.10.4. I tried several

Hi all, I am referring to the official wiki here: https://wiki.samba.org/index.php/Setting_up_a_home_share#Setting_up_the_share_and_filesystem_permissions I was struggling around for many hours before I have found out what caused my issue. Well, I have created the [home] share exactly as epxlained on the How-To, in detail: I am creating on the linux prompt at the member server the directory with

>> Side question: How is it even possible that Windows "remembers" the >> ACL it sets but it's not visible on Linux when using getfacl? Windows ACLs are being stored in Extended Attributes using the acl_xattr vfs module. Linux ACLs are not there because the line acl_xattr:ignore system acls = yes is telling Samba not to write them. On 13 May 2018 21:25, Viktor

>> Side question: How is it even possible that Windows "remembers" the >> ACL it sets but it's not visible on Linux when using getfacl? Windows ACLs are being stored in Extended Attributes using the acl_xattr vfs module. Linux ACLs are not there because the line acl_xattr:ignore system acls = yes is telling Samba not to write them. On 13 May 2018 21:25, Viktor

Alright, even with that change they cannot access the share. I do not have SELinux on this system to my knowledge. The only change since my initial post was changing SAMDOM in my config to TRUEVINE as was pointed out. I then rebooted the server for good measure. People in the AD group FBC are still debied access to the FBC share and people in the AD administration group are still denied access to

Hello, i also fired up a new vm :) and configured "rid" backend. I followed all step in https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs. Sett the Attributs in smb.conf: vfs objects = acl_xattr map acl inherit = yes store dos attributes = yes Granting the SeDiskOperatorPrivilege: # net rpc rights grant "SAMDOM\Domain Admins" SeDiskOperatorPrivilege

I have been using Samba4 for ages and love it as a DC and a print-server. I just setup my first member-server designed solely to host file shares, and have hit an issue. Group policy is mapping it correctly for the users in the group, but those users are getting an access denied message from their Windows 7 Pro 64bit clients when accessing the share. I have configured ACLs and the box

On Thu, 18 Apr 2019 14:29:30 -0400 Bob Smith <bobs04475 at gmail.com> wrote: > Hello Rowland, > > Thank you for the suggested link! > > I followed "Using POSIX ACLs on a Unix domain member" also. Don't ;-) Use Windows acls > "Granting the SeDiskOperatorPrivilege Privilege" > # net rpc rights grant "SAMDOM\Domain Admins"

On 2019-12-08 15:01, Rowland penny via samba wrote: > On 08/12/2019 18:18, Howard Fleming via samba wrote: >> I am building a Samba4 setup to replace a Samba3 server I built for >> small non profit school back in 2012. >> >> It is running CentOS 6.x, samba version 3.6.23-52.el6_10. ?Rather >> than attempt to upgrade this system to Samba4, it makes more sense

On Mon, 8 Oct 2018 18:53:45 +0200 Peter Milesson via samba <samba at lists.samba.org> wrote: > Hi folks, > Problem > ======= > Setting up and managing the shares on the Samba member server differs > significantly from the Samba Wiki documentation. It seems that the > domain Administrator account, and the Domain Admins group haven't got > any elevated privileges

Hi, I am testing 2 samba AD DCs running self compiled 4.7.0rc5 and 2 member servers that are running samba-4.6.2-8.el7.x86_64 that I am trying to get setup as file servers. The file server smb.conf looks like the following: [global] security = ADS workgroup = SAMDOM realm = SAMDOM.MYDOMAIN.COM winbind use default domain = yes idmap config * : backend = tdb idmap