similar to: Can't get 'dos filemode' to work as expected

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

Hi folks, I'm trying to set up a share with samba 2.2.8a (SuSE SLES 8) with ACL support and winbind where every user with write access to a file should be able to change the permissions of that file. According to the man page "dos filemode = yes" should do it - but not for me. It seems that this param is doing nothing at all. I'm I dump ?? What could be wrong here ??

This is somewhat a reincarnation of a problem I am facing since upgrading to samba 3.5.6 (3.5.8 is identical). I use samba on an ext3 ACL enabled file system. Typically a users access rights are determined by his or her membership in different groups. The access right is therefore defined and granted by/to the group, not the user. These groups then appear in the ACL of directories and files

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,

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 =

I have some trouble with a samba 3.5.8 server when setting directory attributes. On a windows XP I execute a small peace of code that calls 'SetFileAttributes' for the directory 'test-dir' located on the samba server. Using log level 10 I find this: [2011/05/26 15:27:02.144060, 3] smbd/process.c:1298 (switch_message) switch message SMBtrans2 (pid 28903) conn 0x7f5e35f0dbb0

Hi, i have a Samba PDC (no LDAP) and added add user script to my config. I can create the user with no problems, login is possible but the /home/samba/profile/user dir is not created. Any hints on that? script commands i added: add user script = /usr/sbin/useradd -m '%u' -g ntusers -G ntusers -s /bin/false delete user script = /usr/sbin/userdel -r '%u' add group script =

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have seen a weird problem in one of my clients. The reported that when issuing a smbmount command (both client and server are CentOS 4.4), it would take up to 30 second for the mount to complete. To make a long history short, by using strace and the source, I noticed smbmnt is first calling mount() using ascii options for *data. Then that would

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]

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

I've now changed the ownership to root, as you suggest. I've removed the ACLs from /shares/DOMAIN - they don't need to be there as anyone can enter this directory already so there's no need for them. The ACLs on my individual home directory: root at server:/shares# getfacl /shares/DOMAIN/username getfacl: Removing leading '/' from absolute path names # file:

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

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

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

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.

Edited smb.conf to match yours and restarted both smbd and winbind. Did not work. Tried to smbclient from another server: session setup failed: NT_STATUS_LOGON_FAILURE. Our member server is also running Ubuntu 14.04 and Samba-4.1.6 (I might have mistakenly wirtten it was 4.1.7 in original email, dont remember now). Domain Users do have gid and users have uids. S pozdravom, Jakub Veselý Správca