similar to: Samba4 binding LDAP Server

Le mar. 20 ao?t 2019 ? 14:30, L.P.H. van Belle via samba <samba at lists.samba.org> a ?crit : > > Hai, > > > > > In short. My network design previously work with Debian Stretch > > Servers and clients and some Windows clients (not many). > > > > Debian Stretch use Samba 4.5.16 so there is no unix_primary_group > > option for the clients. So I have

Le mer. 21 ao?t 2019 ? 14:34, Rowland penny via samba <samba at lists.samba.org> a ?crit : > On 21/08/2019 09:04, Prunk Dump via samba wrote: > > Le mar. 20 ao?t 2019 ? 14:30, L.P.H. van Belle via samba > > <samba at lists.samba.org> a ?crit : > >> Hai, > >> > >>> In short. My network design previously work with Debian Stretch >

Le mer. 21 ao?t 2019 ? 17:04, Rowland penny via samba <samba at lists.samba.org> a ?crit : > > On 21/08/2019 15:14, Prunk Dump via samba wrote: > > Le mer. 21 ao?t 2019 ? 14:34, Rowland penny via samba <samba at lists.samba.org> > > a ?crit : > > > >> On 21/08/2019 09:04, Prunk Dump via samba wrote: > >>> Le mar. 20 ao?t 2019 ? 14:30, L.P.H.

Hi everybody, I've searched deeply into the samba wiki and the list for some working examples, but I cannot find my way out, I'm a kind of rough samba user (let's say almost newbie).. so asking help here: This is my setup: DC (samba.my.domain.com <http://samba.my.domain.com/>): CentOS 6.5 with sernet-samba 4.1.6 started in "ad" mode (upgraded successfully from

Hi, I have a case where I only want to restrict access to SMB shares via filesystem permissions (and POSIX ACLs). Therefore, I do not want Samba to verify security in any way at the SMB level. If the filesystem/ACL permissions allow access to the shared directory, so should Samba. If the filesystem does not allow access to the filesystem, Samba should deny as well. I thought I had this

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

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 list, I'm having one of those 'I'm stupid' -problems with LVM on CentOS 5.2. I've been working with traditional partitions until now, but I've finally been sold on the theoretical benefits of using LVM, but for now I only have a huge pile of broken filesystems to show for my efforts. My scenario; I attach a disk, either over USB or iSCSI. I create a PV on this

I am facing a strange problem related to authentication of NT users accessing the SAMBA server. Here are the details: Server: Solaris 9, SUN Ultra 60, SAMBA 2.2.7a with PAM and WINBIND Client: Windows XP, NT4.0, 2000 Symptoms: Created a share \\server\test (UNIX: /export/SMB/test) with access to group 'TestGoup' where 'TestUser' is a member. 'TestUser' is a member of

I am having a problem getting Samba to use the linux group membership when following a symlink. On the Linux side, I have a soft link from the user's home directory to the shared directory. ln -s /home/shared/testgroup testshare In the smb.conf I have: [homes] comment = Home Directories browseable = no writable = yes valid users = %S force create mode = 0660 delete

Am 11.02.19 um 14:22 schrieb Rowland Penny via samba: > On Mon, 11 Feb 2019 13:46:05 +0100 > Matthias Leopold via samba <samba at lists.samba.org> wrote: > >> >> >> Am 11.02.19 um 13:22 schrieb Rowland Penny via samba: >>> On Mon, 11 Feb 2019 12:30:51 +0100 >>> Matthias Leopold via samba <samba at lists.samba.org> wrote: >>>

Hi, we are using a _single_ LDAP server as backend for _multiple_ Samba standalone file servers (security=user). This LDAP server serves mainly other purposes and access for Samba is read only so the situation is not optimal but "it works for us". Still I don't understand one phenomenon concerning visibility of LDAP groups. The LDAP configuration in smb.conf for all our Samba

Am 11.02.19 um 13:22 schrieb Rowland Penny via samba: > On Mon, 11 Feb 2019 12:30:51 +0100 > Matthias Leopold via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> we are using a _single_ LDAP server as backend for _multiple_ Samba >> standalone file servers (security=user). This LDAP server serves >> mainly other purposes and access for Samba is

Hi all, After setting permissions on a file. If anyone authorised to open the file writes to it, the ACL gets deleted and that person becomes the owner of the file and the group is reset to the default. For example, whenever a certain user opens and changes a file in the problem folder he becomes the owner and another gets kicked of the list: More clearly, lee was the last one to write to this

Hello, I'm having trouble when I try do get a group SID from my domain, the user lookup and authentication is working fine. Actually what I'm trying to do is to authenticate squid against MS AD using winbind. I need to restrict access by group, so I'm using wbinfo_group.pl to do it. The machine has been built to be a proxy server only. I'm using Suse Linux 9.3 Professional

Am 11.02.19 um 16:33 schrieb Rowland Penny via samba: > On Mon, 11 Feb 2019 15:40:02 +0100 > Matthias Leopold via samba <samba at lists.samba.org> wrote: > >> >> >> Am 11.02.19 um 14:22 schrieb Rowland Penny via samba: >>> On Mon, 11 Feb 2019 13:46:05 +0100 >>> Matthias Leopold via samba <samba at lists.samba.org> wrote: >>>

Hi, I've been running a samba server with winbind (CentOS 7) as a member of an AD Domain (Windows 2012 R2) for several months without a problem. "Suddenly" I'm seeing the problem that the membership in newly created AD groups isn't correctly visible for some users on the samba server or only after some indefinite amount of time. I'm looking simply at the output of

Hai, > > In short. My network design previously work with Debian Stretch > Servers and clients and some Windows clients (not many). > > Debian Stretch use Samba 4.5.16 so there is no unix_primary_group > option for the clients. So I have to use the "dirty" tweak of > modifying all my users "primaryGroupID" to the corresponding >

On 21/08/2019 09:04, Prunk Dump via samba wrote: > Le mar. 20 ao?t 2019 ? 14:30, L.P.H. van Belle via samba > <samba at lists.samba.org> a ?crit : >> Hai, >> >>> In short. My network design previously work with Debian Stretch >>> Servers and clients and some Windows clients (not many). >>> >>> Debian Stretch use Samba 4.5.16 so there is

On 21/08/2019 15:14, Prunk Dump via samba wrote: > Le mer. 21 ao?t 2019 ? 14:34, Rowland penny via samba <samba at lists.samba.org> > a ?crit : > >> On 21/08/2019 09:04, Prunk Dump via samba wrote: >>> Le mar. 20 ao?t 2019 ? 14:30, L.P.H. van Belle via samba >>> <samba at lists.samba.org> a ?crit : >>>> Hai, >>>>