similar to: Problems with inconsistent ACL inheritance and permissions after Samba upgrade

On 11/06/19 11:49, Rowland penny via samba wrote: > On 11/06/2019 11:38, Sebastian Arcus via samba wrote: >> >> On 11/06/19 11:07, Rowland penny via samba wrote: >>> On 11/06/2019 10:34, Sebastian Arcus via samba wrote: >>>> I've just upgraded a Samba AD server to 4.10.2 a few weeks ago from >>>> 4.x (I'm afraid I'm not sure the exact

On 11/06/19 13:29, Rowland penny via samba wrote: > On 11/06/2019 13:13, Sebastian Arcus via samba wrote: >> >> On 11/06/19 11:49, Rowland penny via samba wrote: >>> On 11/06/2019 11:38, Sebastian Arcus via samba wrote: >>>> >>>> On 11/06/19 11:07, Rowland penny via samba wrote: >>>>> On 11/06/2019 10:34, Sebastian Arcus via samba

On 11/06/19 11:07, Rowland penny via samba wrote: > On 11/06/2019 10:34, Sebastian Arcus via samba wrote: >> I've just upgraded a Samba AD server to 4.10.2 a few weeks ago from >> 4.x (I'm afraid I'm not sure the exact earlier version) - and since >> then I just haven't managed to pin down the file permissions and >> inheritance on the shares as

On 11/06/2019 13:13, Sebastian Arcus via samba wrote: > > On 11/06/19 11:49, Rowland penny via samba wrote: >> On 11/06/2019 11:38, Sebastian Arcus via samba wrote: >>> >>> On 11/06/19 11:07, Rowland penny via samba wrote: >>>> On 11/06/2019 10:34, Sebastian Arcus via samba wrote: >>>>> I've just upgraded a Samba AD server to 4.10.2 a

On 11/06/19 16:44, Sebastian Arcus via samba wrote: > > On 11/06/19 14:54, Sebastian Arcus via samba wrote: >> >> On 11/06/19 13:29, Rowland penny via samba wrote: >>> On 11/06/2019 13:13, Sebastian Arcus via samba wrote: >>>> >>>> On 11/06/19 11:49, Rowland penny via samba wrote: >>>>> On 11/06/2019 11:38, Sebastian Arcus via

On 11/06/19 14:54, Sebastian Arcus via samba wrote: > > On 11/06/19 13:29, Rowland penny via samba wrote: >> On 11/06/2019 13:13, Sebastian Arcus via samba wrote: >>> >>> On 11/06/19 11:49, Rowland penny via samba wrote: >>>> On 11/06/2019 11:38, Sebastian Arcus via samba wrote: >>>>> >>>>> On 11/06/19 11:07, Rowland penny

On 11/06/2019 10:34, Sebastian Arcus via samba wrote: > I've just upgraded a Samba AD server to 4.10.2 a few weeks ago from > 4.x (I'm afraid I'm not sure the exact earlier version) - and since > then I just haven't managed to pin down the file permissions and > inheritance on the shares as it's been constantly causing issues. This > server is both a file

On 11/06/2019 11:38, Sebastian Arcus via samba wrote: > > On 11/06/19 11:07, Rowland penny via samba wrote: >> On 11/06/2019 10:34, Sebastian Arcus via samba wrote: >>> I've just upgraded a Samba AD server to 4.10.2 a few weeks ago from >>> 4.x (I'm afraid I'm not sure the exact earlier version) - and since >>> then I just haven't managed to

I believe I have found either a bug or something I do not understand. I recently had a file-share issue and the resolution was to set the "others" permissions to 5, read and execute. The problem with this is that once I am in Windows on a workstation, this appears to allow "Everyone", "CREATOR OWNER", and "CREATOR GROUP" access. We normally setup our

On 12/03/18 11:28, Rowland Penny via samba wrote: > On Mon, 12 Mar 2018 11:11:44 +0000 > Sebastian Arcus via samba <samba at lists.samba.org> wrote: > >> I have a Samba AD running Samba 4.7.5. Everything was working fine, >> when, seemingly out of the blue, the users started to be denied >> access to all shares. If I try from a Windows 7 or Windows 10 >>

I have a Samba AD running Samba 4.7.5. Everything was working fine, when, seemingly out of the blue, the users started to be denied access to all shares. If I try from a Windows 7 or Windows 10 machine, logged in as a user in "Domain Uses", I get: "Windows cannot access \\server-name\share_name. You do not have permission to access \\server-name\share_name" If I use

On 12/03/18 12:56, Rowland Penny via samba wrote: > On Mon, 12 Mar 2018 11:36:47 +0000 > Sebastian Arcus via samba <samba at lists.samba.org> wrote: > >> >> On 12/03/18 11:28, Rowland Penny via samba wrote: >>> On Mon, 12 Mar 2018 11:11:44 +0000 >>> Sebastian Arcus via samba <samba at lists.samba.org> wrote: >>> >>>> I have a

After a decent amount of online searches, I am a little bit lost on the subject of Samba4 in AD mode and ACL's. Could anybody help with the following please: 1. Is it correct that my default ACL's are being ignored (new files created don't follow the default ACL's permissions of the parent folder) because "inherit permissions = " is set to No by default in smb.conf?

> You could try using a script Louis wrote, see here: > https://github.com/thctlo/samba4/blob/master/samba-check-set-sysvol.sh > > The 'idmap config' lines are nothing to worry about, you cannot set them on a DC, but, for some reason, testparm etc warns about > them. > > Rowland > Sorry, I should have said - I ran louis' script and set the acl's according

Has anyone seen this when they do a getfacl on a samba share? [root@gfm-atlas GFM_Shares]# getfacl Installpoint/ # file: Installpoint # owner: root # group: AVMAX+domainadmins user::rwx group::rwx group:AVMAX+domain\040users:r-x mask::rwx other::--- default:user::rwx default:group::rwx default:group:AVMAX+domain\040users:r-x default:mask::rwx default:other::--- Notice the

> It's needed after every GPO addition and edit. There must be a root > cause to hunt down somewhere. Or is it a bug in 4.13.0 ? Yes, and no. Yes, its a bug. No, in my opionion its an old setting thats just needs some updating. Try this. samba-tool ntacl set "O:LAG:BAD:P(A;OICI;0x001f01ff;;;BA)(A;OICI;0x001200a9;;;SO)(A;OICI;0x001f01

Hi, on our samba 4 domain member server we use the vfs objects module 'recycle'. Unfortunately we ran into a strange permission problem with deleted folders. The newly created folders in the recycle folder have the wrong permission. The deleted file(s) itself has the correct group (rw) permissions. The shares correct permissions: getfacl Papierkorb/ # file: Papierkorb/ # owner: root #

Hi, On a samba 4.9.4 fileserver using ad backend with rfc2307  , when i create a file from a Win10 client, it s always created with the rights user:"domain users". I ve understood that with "unix_primary_group = yes" , the file should be created with the rights user:gidNumber . Here is my config : [global]        security = ADS        workgroup = SAMBA494        realm =

I've set up a profiles share according to the wiki article: https://wiki.samba.org/index.php/Implementing_roaming_profiles Users are able to create new roaming profiles and they cannot browse each others' profiles, so all that is working. The only issue is that the group "domain admins" does not have privileges to read or delete user profiles. The acls on the profiles directory

Hello, My name is Hiro. I'm using samba 3.0.21b-2(acl) and RHEL4.1(kernel 2.6.9-11.ELsmp) + AD Server Following problem: When the attribute of the group of the folder was set to a full control twice, the member of the group became inaccessible. I want to know this problem is BUG or SPEC. One example [smb.conf] security = ADS acl check permissions = no acl group control = no acl map