Mac SMB Share Permissions Issue

[_kstone]

Morning all,

 

Been having all manner of Mac permissions issues for a while and i've found some fixes for a few bits but still boggled by one thing.

 

Our mac users are accessing a windows share via SMB. They authenticate with their AD accounts (Macs are bound to AD). They can access the files/folders as needed on the share. They can create new files/folders and all users can access and read these.

 

The users will copy a folder down to their Mac to work on it, then want to share these between each others Macs.

 

When a folder is copied from the SMB share, its permissions are amended to owner r/w, everyone no access. So we have to do a manual tweak of the permissions to allow everyone r/w access. This is time consuming and not ideal.

 

We had a similar issue with this happening on files made on their macs, but I have used a custom umask so that all new files/folders have everyone r/w by default, which works well. However, for the Windows share, this doesn't apply, and it doesn't seem to use the NTFS permissions when copying to the mac.

 

How can I make it so that when files are copied to the Mac, they keep the permissions from the SMB share, rather than generate new restricted permissions?

 

I've tried accessing via CIFS, which has been suggested on various articles.

 

Any help, much appreciated!

[Brimstone]

This has been a known issue with no real workaround or fix for many years, ditch PM.

 

https://arstechnica.com/civis/viewtopic.php?f=19&t=1385233

[unixman_again]

When a folder is copied from the SMB share, its permissions are amended to owner r/w, everyone no access. So we have to do a manual tweak of the permissions to allow everyone r/w access. This is time consuming and not ideal.

 

Cron (what windoze calls Scheduled Task) is your friend here. We run one on the M$ server to set the perms on files copied from the Macs.

[_kstone]

Thanks for your responses, not sure either of you have understood my issue.

 

The issue is that NTFS permissions do not travel with folders when copied from the Windows Share to the Macbook. Meaning that only the user that copied the file has access. I need to change the default permissions that files come down with.

[bknaggs]

What happens if the files are opened directly from the server rather than being copied to the Mac first?

[_kstone]

When accessed on the server, the files have the correct permission as per NTFS.

 

Our users need to be able to copy from the server then share between macbooks directly.

[bknaggs]

It sounds like it’s being processed as an NTFS move rather than an NTFS copy when it is going from the Mac to the server. If I’ve got time I’ll have a look at one of our Macs tomorrow and see what happens when copying from the Mac to a Windows file server.

[_kstone]

It’s not Mac to Windows Share that Is the issue. It’s Windows Share to Mac!

[bknaggs]

Ah right. Sorry can’t help as our Macs aren’t setup to share to each other.

[_kstone]

You’d be able to see if you copy a file from the Windows Share to the Mac, then check permissions on the file on the Mac. In my scenarios it’s giving current user r/w, everyone no access. Or 700 in unix permissions speak.

[Marci]

Sounds like a default uMask / samba create mask issue. Try...

 

sudo pico /etc/nsmb.conf

 

It probably doesn't exist... set it's content to:

 

[global]
inherit permissions = yes

[default]
create mask = 0664 
force create mode = 0664
directory mask = 0755 
force directory mode = 0755

 

Caveat: _i think_!

 

(ctrl-o to save, ctrl-x to exit, reboot, give it a try. If no different, remove /etc/nsmb.conf and reboot to undo the changes. If different, but the set permissions are still not quite right, post back with what perms files turn up with - I can't remember whether create mask etc in nsmb.conf uses actual final permissions or subtractive permissions)

[Marci]

EDIT: Scratch all that - no longer works in Sierra / High Sierra since switching from smb.conf to nsmb.conf. Sorry!