Mac OS File Sharing and Windows Client (Permission)
I've a Mac Mini which I want to use as file server. I've the following directory structure that I want to share:
Public <-- shared (UserA and UserB readonly; Admin is owner)
|- FolderA <-- (UserA is owner, read and write; UserB readonly)
|- FolderB <-- (UserB is owner, read and write; UserA readonly)
I've I access the public share from a Mac client and UserA for examples creates a new subfolder in FolderA then UserB can read it.
But I've UserB for examples creates a new subfolder in FolderB from a PC client (Windows 10) then UserA cannot read it.
I've I take a look at the permissions it looks like that:
Public <-- shared (UserA and UserB readonly; Admin is owner)
|- FolderA <-- (UserA is owner, read and write; UserB readonly)
|- MacSubFolderA <-- (UserA is owner, read and write; UserB readonly)
|- FolderB <-- (UserB is owner, read and write; UserA readonly)
|- MacSubFolderB <-- (UserB is owner, read and write; UserA readonly)
|- PCSubFolderB <-- (UserB is owner, read and write; UserA has no access, WHY?)
I know the following workaround. I can apply the file permission of FolderB for all subfolders. But I don't want to do that by hand every time a PC client adds some files.
macos file-permissions file-sharing
asked Jan 4 at 9:16
WollmichWollmich
208114
add a comment |
I've a Mac Mini which I want to use as file server. I've the following directory structure that I want to share:
Public <-- shared (UserA and UserB readonly; Admin is owner)
|- FolderA <-- (UserA is owner, read and write; UserB readonly)
|- FolderB <-- (UserB is owner, read and write; UserA readonly)
I've I access the public share from a Mac client and UserA for examples creates a new subfolder in FolderA then UserB can read it.
But I've UserB for examples creates a new subfolder in FolderB from a PC client (Windows 10) then UserA cannot read it.
I've I take a look at the permissions it looks like that:
Public <-- shared (UserA and UserB readonly; Admin is owner)
|- FolderA <-- (UserA is owner, read and write; UserB readonly)
|- MacSubFolderA <-- (UserA is owner, read and write; UserB readonly)
|- FolderB <-- (UserB is owner, read and write; UserA readonly)
|- MacSubFolderB <-- (UserB is owner, read and write; UserA readonly)
|- PCSubFolderB <-- (UserB is owner, read and write; UserA has no access, WHY?)
I know the following workaround. I can apply the file permission of FolderB for all subfolders. But I don't want to do that by hand every time a PC client adds some files.
macos file-permissions file-sharing
asked Jan 4 at 9:16
WollmichWollmich
208114
1
Does your problem sound similar to this one? apple.stackexchange.com/questions/139736/… In that case, maybe that's the solution.
– PaulJ
Jan 4 at 10:46
add a comment |
I've a Mac Mini which I want to use as file server. I've the following directory structure that I want to share:
Public <-- shared (UserA and UserB readonly; Admin is owner)
|- FolderA <-- (UserA is owner, read and write; UserB readonly)
|- FolderB <-- (UserB is owner, read and write; UserA readonly)
I've I access the public share from a Mac client and UserA for examples creates a new subfolder in FolderA then UserB can read it.
But I've UserB for examples creates a new subfolder in FolderB from a PC client (Windows 10) then UserA cannot read it.
I've I take a look at the permissions it looks like that:
Public <-- shared (UserA and UserB readonly; Admin is owner)
|- FolderA <-- (UserA is owner, read and write; UserB readonly)
|- MacSubFolderA <-- (UserA is owner, read and write; UserB readonly)
|- FolderB <-- (UserB is owner, read and write; UserA readonly)
|- MacSubFolderB <-- (UserB is owner, read and write; UserA readonly)
|- PCSubFolderB <-- (UserB is owner, read and write; UserA has no access, WHY?)
I know the following workaround. I can apply the file permission of FolderB for all subfolders. But I don't want to do that by hand every time a PC client adds some files.
macos file-permissions file-sharing
asked Jan 4 at 9:16
WollmichWollmich
208114
I've a Mac Mini which I want to use as file server. I've the following directory structure that I want to share:
Public <-- shared (UserA and UserB readonly; Admin is owner)
|- FolderA <-- (UserA is owner, read and write; UserB readonly)
|- FolderB <-- (UserB is owner, read and write; UserA readonly)
I've I access the public share from a Mac client and UserA for examples creates a new subfolder in FolderA then UserB can read it.
But I've UserB for examples creates a new subfolder in FolderB from a PC client (Windows 10) then UserA cannot read it.
I've I take a look at the permissions it looks like that:
Public <-- shared (UserA and UserB readonly; Admin is owner)
|- FolderA <-- (UserA is owner, read and write; UserB readonly)
|- MacSubFolderA <-- (UserA is owner, read and write; UserB readonly)
|- FolderB <-- (UserB is owner, read and write; UserA readonly)
|- MacSubFolderB <-- (UserB is owner, read and write; UserA readonly)
|- PCSubFolderB <-- (UserB is owner, read and write; UserA has no access, WHY?)
I know the following workaround. I can apply the file permission of FolderB for all subfolders. But I don't want to do that by hand every time a PC client adds some files.
macos file-permissions file-sharing
macos file-permissions file-sharing
asked Jan 4 at 9:16
WollmichWollmich
208114
asked Jan 4 at 9:16
WollmichWollmich
208114
asked Jan 4 at 9:16
WollmichWollmich
208114
asked Jan 4 at 9:16
WollmichWollmich
208114
asked Jan 4 at 9:16
WollmichWollmich
208114
208114
1
Does your problem sound similar to this one? apple.stackexchange.com/questions/139736/… In that case, maybe that's the solution.
– PaulJ
Jan 4 at 10:46
add a comment |
1
Does your problem sound similar to this one? apple.stackexchange.com/questions/139736/… In that case, maybe that's the solution.
– PaulJ
Jan 4 at 10:46
1
1
Does your problem sound similar to this one? apple.stackexchange.com/questions/139736/… In that case, maybe that's the solution.
– PaulJ
Jan 4 at 10:46
Does your problem sound similar to this one? apple.stackexchange.com/questions/139736/… In that case, maybe that's the solution.
– PaulJ
Jan 4 at 10:46
add a comment |
1 Answer
1
active
oldest
votes
The solution is to set up ACL inheritance permissions on the parent folders FolderA and FolderB.
First enable ACL permissions for SMB shares with the following command.
sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.smb.server AclsEnabled -bool YES
Second create an UserGroup that contains UserA and UserB.
Then set up inheritance permissions on the parent folders FolderA and FolderB with the following two commands.
sudo chmod -R +a "group:UserGroup:allow readattr,readextattr,readsecurity,list,search,file_inherit,directory_inherit" /Public/FolderA
sudo chmod -R +a "group:UserGroup:allow readattr,readextattr,readsecurity,list,search,file_inherit,directory_inherit" /Public/FolderB
Source: https://apple.stackexchange.com/a/139762
answered Jan 5 at 7:33
WollmichWollmich
208114
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390437%2fmac-os-file-sharing-and-windows-client-permission%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The solution is to set up ACL inheritance permissions on the parent folders FolderA and FolderB.
First enable ACL permissions for SMB shares with the following command.
sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.smb.server AclsEnabled -bool YES
Second create an UserGroup that contains UserA and UserB.
Then set up inheritance permissions on the parent folders FolderA and FolderB with the following two commands.
sudo chmod -R +a "group:UserGroup:allow readattr,readextattr,readsecurity,list,search,file_inherit,directory_inherit" /Public/FolderA
sudo chmod -R +a "group:UserGroup:allow readattr,readextattr,readsecurity,list,search,file_inherit,directory_inherit" /Public/FolderB
Source: https://apple.stackexchange.com/a/139762
answered Jan 5 at 7:33
WollmichWollmich
208114
add a comment |
The solution is to set up ACL inheritance permissions on the parent folders FolderA and FolderB.
First enable ACL permissions for SMB shares with the following command.
sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.smb.server AclsEnabled -bool YES
Second create an UserGroup that contains UserA and UserB.
Then set up inheritance permissions on the parent folders FolderA and FolderB with the following two commands.
sudo chmod -R +a "group:UserGroup:allow readattr,readextattr,readsecurity,list,search,file_inherit,directory_inherit" /Public/FolderA
sudo chmod -R +a "group:UserGroup:allow readattr,readextattr,readsecurity,list,search,file_inherit,directory_inherit" /Public/FolderB
Source: https://apple.stackexchange.com/a/139762
answered Jan 5 at 7:33
WollmichWollmich
208114
add a comment |
The solution is to set up ACL inheritance permissions on the parent folders FolderA and FolderB.
First enable ACL permissions for SMB shares with the following command.
sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.smb.server AclsEnabled -bool YES
Second create an UserGroup that contains UserA and UserB.
Then set up inheritance permissions on the parent folders FolderA and FolderB with the following two commands.
sudo chmod -R +a "group:UserGroup:allow readattr,readextattr,readsecurity,list,search,file_inherit,directory_inherit" /Public/FolderA
sudo chmod -R +a "group:UserGroup:allow readattr,readextattr,readsecurity,list,search,file_inherit,directory_inherit" /Public/FolderB
Source: https://apple.stackexchange.com/a/139762
answered Jan 5 at 7:33
WollmichWollmich
208114
The solution is to set up ACL inheritance permissions on the parent folders FolderA and FolderB.
First enable ACL permissions for SMB shares with the following command.
sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.smb.server AclsEnabled -bool YES
Second create an UserGroup that contains UserA and UserB.
Then set up inheritance permissions on the parent folders FolderA and FolderB with the following two commands.
sudo chmod -R +a "group:UserGroup:allow readattr,readextattr,readsecurity,list,search,file_inherit,directory_inherit" /Public/FolderA
sudo chmod -R +a "group:UserGroup:allow readattr,readextattr,readsecurity,list,search,file_inherit,directory_inherit" /Public/FolderB
Source: https://apple.stackexchange.com/a/139762
answered Jan 5 at 7:33
WollmichWollmich
208114
answered Jan 5 at 7:33
WollmichWollmich
208114
answered Jan 5 at 7:33
WollmichWollmich
208114
answered Jan 5 at 7:33
WollmichWollmich
208114
208114
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390437%2fmac-os-file-sharing-and-windows-client-permission%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Does your problem sound similar to this one? apple.stackexchange.com/questions/139736/… In that case, maybe that's the solution.
– PaulJ
Jan 4 at 10:46