Here's the set-up:
I have a server running Samba with a share called "MyShare". MyShare contains a folder that, on the Server's file system is owned by user "User1" and Group "Employees". The folder and it's files are 770 and 660 respectively. Owner and group read/write, no world access.
The Share definition is:
[MyShare] comment = MyShare path = /home/samba/Shares/MyShare browsable = yes guest ok = yes read only = no force group = +Employees inherit permissions = yes
On the Server, User1, User2, User3, etc. are all members of the "Employees" group. The theory is that any member of the group can work on any file owned by the group regardless of owner (who created it).
On the Clients, the UIDs are arbitrary (they don't match the server UIDs) and the "Employees" group does not exist.
When I ssh into the Server as "User2", I can see and read/write all of the files (even though User1 is the owner) because I'm a member of the "Employees" group, the files and folder are group-owned by "Employees", and the files and folders are group read/writeable. This is as expected.
The problem comes when accessing this share through Samba from an Ubuntu Client machine.
I mount the share with /etc/fstab as:
//192.168.1.100/MyShare /media/samba/MyShare cifs noperm,credentials=/root/smb/creds,rw,iocharset=utf8,uid=1000 0 0
It mounts OK, but it treats me as if I am not a member of the "Employees" group. In other words, I can access files I own (user2), but not "Employees" group owned files, since it doesn't think I'm a member of the "Employees" group.
How do I get Samba to acknowledge User2's membership of the "Employees" group?