similar to: Unable to access shares

> >>>> Run this : getfacl /home/users > >>> getfacl: Removing leading '/' from absolute path names > >>> # file: home/users > >>> # owner: root > >>> # group: A\\domain\040admins > >>> user::rwx > >>> user:root:rwx > >>> user:10512:rwx > >>> group::rwx > >>>

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

Im not saying anything but having a GID on "domain admins" works fine. For me then since 2014.. getent group "domain admins" domain admins:x:10001:admin,administrator Can you post the output of ls -ald /data/samba What happens when you do this. chmod 1777 /data/samba/profiles or 3777, but that opens access for "domain users" to the users profiles folders. But

Hello everybody, I been at this for more then a week and went through the archives and wiki but can not get it to work. I been trying to follow these steps: https://wiki.samba.org/index.php/User_Home_Folders wanted behavior: samba-tool user create jdoe pass01 --login-shell /bin/bash --given-name "John Doe" --home-drive=H --home-directory="\\\SAMBA01\users\jdoe

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

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

[global] netbios name = aphrodite security = ADS workgroup = SAMDOM realm = AD.SAMDOM.COM.AU log file = /var/log/samba/%m.log log level = 1 dedicated keytab file = /etc/krb5.keytab kerberos method = secrets and keytab winbind refresh tickets = yes winbind trusted domains only = no winbind use default domain = yes

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

Dear all, I have set a small test domain in virtualbox. 1. Samba AD DC on Debian bullseye testing 4.11.6 2. Samba domain member Debian Stretch 4.10.14 3. Windows 10 Enterprise evaluation version 1909 Roaming profiles with folder redirection setup. PAM working. The above was setup basically using guides in wiki.samba.org, with nearly the only thing changed was SAMDOM to SAMBA. "Unix

On Mon, 12 Mar 2018 13:17:19 +0000 Sebastian Arcus via samba <samba at lists.samba.org> wrote: > On 12/03/18 12:56, Rowland Penny via samba wrote: > > > > I don't think this is your main problem though, did the problem > > start after a windows update ? > > I think your clients are possibly trying to connect with NTLMv2 > > If that was the case,

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

On Thu, Aug 2, 2018 at 1:55 PM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Thu, 2 Aug 2018 13:16:26 -0400 > pisymbol via samba <samba at lists.samba.org> wrote: > > > On Thu, Aug 2, 2018 at 1:11 PM, Eric Altman via samba > > <samba at lists.samba.org > > > wrote: > > > > > > > > It’s just that the mount has

On Wed, 30 Aug 2017 12:20:04 +0200 (CEST) Gaetan SLONGO <gslongo at it-optics.com> wrote: > > Hi Rowland My test SMB have several test lines and is dirty, for sure > not correct :-) Could you share your setup to achieve this ? > This is my working smb.conf (note: I use Samba 4.6.x) [global] workgroup = SAMDOM security = ADS realm = SAMDOM.EXAMPLE.COM #

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

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

On 05/01/15 14:59, James wrote: > That is actually the wiki page I am currently referencing in my > question. From the wiki you can see the 'Everyone' group. I would > normally remove and add domain users or authenticated users. That > prompted me to ask myself "what if I wanted the everyone group to have > access"? How does the member server know who the

On Tue, 9 Oct 2018 22:16:41 +0200 Peter Milesson <miles at atmos.eu> wrote: > > > On 09.10.2018 21:25, Rowland Penny via samba wrote: > > On Tue, 9 Oct 2018 19:44:55 +0200 > > Peter Milesson via samba <samba at lists.samba.org> wrote: > > > >> Hi Rowland, > >> > >> I made a fresh install of the AD DC, a member server, and a

Hi folks, Hardware/OS =========== - Samba AD DC ver. 4.9.1 (compiled using standard CentOS tools and libraries) functions only as AD server (authentication, AD services), migrated from old Samba NT PDC through classicupgrade, OS CentOS 7.5, kernel 4.9.40 (elrepo-lt), VM under Xen 4.9.0 - Samba AD member server ver. 4.7.1 (from distribution) with different shares for different user groups,