similar to: Parameter 'dos filemode' - I'm giving up !

Hi, I've a question about the 'dos filemode' option (samba 3.0.24, debian etch). I want to use this option to allow group members with write access to add/change permissions. man smb.conf: dos filemode (S) only the owner of a file/directory is able to change the permissions on it. However, this behavior is often confusing to DOS/Windows users. Enabling this parameter allows a

According to the smb.conf man page, the "dos filemode" parameter will allow a user who is not the owner of a file to affect permissions changes on a file or folder provided he has write access to that object. This does not appear to be the case. Users with write access via user or group ACEs receive an "Access denied" error when attempting to make ACL changes via windows,

Hello, After an upgrade to samba 3.5.8 (from 3.2.5) the option 'dos filemode' does not seem to work anymore. If I (as a user) do not own the file I can't change permissions. I am user 'felix' and member of supplementary group 'Development'. To test things I use the following share definition: [Temp] path = /srv/samba/file-shares/tmp browseable =

dear all, switching from 3.0.22 to 3.023b, we can't get the parameter "dos filemode" to work (giving members of a group with full control the ability to change the acl's). in previous versions we were using "acl group control" which served well (now marked deprecated). the share section of smb.conf is: [test] comment = testshare path = /media/samba/test public =

Hi, I'm using the "dos filemode" option to get Windows like acl handling. Now I noticed the following line: "Note that a user belonging to the group owning the file will not be allowed to change permissions if the group is only granted read access" Is there anyway to achive this so the group can change permissions even when the group has read-only rights? This is exacly

Dear all I struggle with a very annoying bug ! The problem is very simple to reproduce (NO Windows stuff needed, ONLY Linux !): 1. Samba 3.5.6 running on a Debian 6 (Squeeze) Server with following configuration: /etc/samba/smb.conf: security = user guest account = nobody map to guest = bad user null passwords = yes case sensitive = yes [myshare]

Hello, i see a strange behavior with timestamps of files on a samba share (4.2.6 on SLES 12 SP1 and 4.1.8 on Ubuntu 14.04) with "dos filetime resolution = yes": On older samba versions, windows properties dialogue correctly shows only even seconds, but (at least) the two indicated versions show sometimes even and sometimes odd seconds if the file has on the server filesystem a

We have Fedora Core 2, samba-3.0.3-5, kernel 2.6.5 We set acl support in fstab We configured samba with acl support + openldap 2.1.29 as passwd backend. In a shared folder "testshare" we set the following directives: [testshare] comment = ...... path = /home/testshare read only = no nt acl support = yes create mask = 0700 directory mask = 0700 security mask = 0777 directory security

Hi! I created a Samba4 Demo Server to test AD functionality. Basically it's a Debian Wheezy machine with a manually compiled Samba4 (smbstatus -V: Version 4.1.0pre1-GIT-051a1a9) according to https://wiki.samba.org/index.php/Samba4/HOWTO but adjusted the paths to a more debian way. I can Manage the Server with the Windows Domain Utilities, add users, add groups, add Machines and so

Hello, i had to upgrade a server from 3.6 to 4.0.10. Now i have a problem had already i solved again. The problem is that a machines program is old and require dos filetime resolution = yes but i does not work with the new 4.0.10 [produktion] path=/home/filestore/produktion browseable = yes writable = yes # create mask = 0777 # directory mask = 0777 #

Hi, I have a share (testshare) where different unix groups (testgroup1, testgroup2) should have access to. But I want that new files are only created with 660 permissions. Here are the ACL's of testshare: # file: testshare # owner: ralfgro # group: ve user::rwx group::rwx group:testgroup1:rwx group:testgroup2:rwx mask::rwx other::--- default:user::rwx default:group::---

Would someone please tell me where I can find some good troubleshooting documents to resolve AD authentication issues when using Samba? Is this mailing list the best place? I was able to setup a working WINBIND-Samba setup on CentOS 7.6, but I am required to use SSSD on a different CentOS 7.6 server. Using a test VM, I can get services running, but I can't authenticate from a Mac or

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

So, I have "working" builds of Samba 3.6.10, and 4.0.2 using the traditional build system on AIX, both built with XLC. For historical reasons, we're needing to use 'encrypt passwords = no', so that Samba uses the OS password. The odd thing, is, the 3.6.10 Samba works just fine, but the 4.0.2 doesn't allow connections. Here's the Samba config I'm using on both:

Hello, I have a performance problem when I don't connect using root and/or a user in the "admin users". Configuration: Samba 3.5.11 running on SLES11SP1. The share exported is on a GPFS filesystem and the GPFS vfs object is loaded(not loading it doesn't change the described behaviour) clients: Windows 7 and Windows 2008R2 all at latest update level. [testshare] comment

Hi ... When trying to migrate from samba3 to samba 4.2.2 I am facing a severe problem that bugs me for hours now. I cannot get a samba 4.2.2 fileserver to work with a samba 4.2.2 PDC as a domain member. My scenario: Samba 3 network. PDC and fileserver where Samba 3.6.25. LDAP backend. We can't move to AD right now so I wanted to move to the current 4.2.2 at least to do this step but to

I am confused (nothing new there ...). I have 2 Ubuntu 9.10 Samba servers. I am trying to mount a share from the other (i.e., "workhorse" is trying to mount a share on "dual-booter"). If I specify a smbmount command with a -k option, I can mount the share: turgon at workhorse:~$ klist Ticket cache: FILE:/tmp/krb5cc_1000 Default principal: turgon at DACRIB.LOCAL Valid starting

Hello, Our samba fileserver is a member of a Windows 2008R2 domain, and has different shares. These shares are set with a "read only = yes" and have an explicit "write list". This works as planned. But when an "read only" user opens a pdf with Adobe acrobat, the file gets DenyMode DENY_WRITE and the user who can edit the file can't save the document anymore.

I think this wont work since the user connectig isnt known in the AD, since the user connecting is mapped to user nobody. auth_check_password_send: Checking password for unmapped user []\[]@[] auth_check_password_send: mapped user is: [CCENTER]\[]@[] connect_acl_xattr: setting 'inherit acls = true' 'dos filemode = true' connect to service IPC$ initially as user NT

Hi all, got the following problem: I'm trying to set up a samba share and want the allowed group to administrate the file and directory permissions on their own. Goal is that everyone in the group can decide via NT security box who - from outside the group - should have read or write permissions on a specific file. I'm using ACL's and everything except this is working fine. Problem