samba access problem 18.04
0
I have setup a samba server on 18.04 and run into a problem with access of sambashares
- user can access his home folder through samba (so I know the [samba]user exists, credentials are recognized)
- same user can not access any sambashare (even though user is in the group required, access rights are
774)
smb.conf looks like this:
[global]
workgroup = WORKGROUP
server string = %h server (Samba, Ubuntu)
dns proxy = no
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
panic action = /usr/share/samba/panic-action %d
server role = standalone server
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = no
passwd program = /usr/bin/passwd %u
passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
pam password change = yes
map to guest = bad user
#============== Share definitions =======================
[samba]
comment = Share for group Warehouse
path = /srv/smb/samba/
browseable = yes
writeable = yes
force create mode = 0660
force directory mode = 0660
Valid users = @sambausers
Any idea, what the root of this trouble may be?
samba
asked May 2 '18 at 13:37
vrmsvrms
96215
bumped to the homepage by Community♦ 10 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
0
I have setup a samba server on 18.04 and run into a problem with access of sambashares
- user can access his home folder through samba (so I know the [samba]user exists, credentials are recognized)
- same user can not access any sambashare (even though user is in the group required, access rights are
774)
smb.conf looks like this:
[global]
workgroup = WORKGROUP
server string = %h server (Samba, Ubuntu)
dns proxy = no
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
panic action = /usr/share/samba/panic-action %d
server role = standalone server
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = no
passwd program = /usr/bin/passwd %u
passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
pam password change = yes
map to guest = bad user
#============== Share definitions =======================
[samba]
comment = Share for group Warehouse
path = /srv/smb/samba/
browseable = yes
writeable = yes
force create mode = 0660
force directory mode = 0660
Valid users = @sambausers
Any idea, what the root of this trouble may be?
samba
asked May 2 '18 at 13:37
vrmsvrms
96215
bumped to the homepage by Community♦ 10 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Run "ls -dl /srv/smb/samba". What group is displayed? If it's not sambausers the remote user will not gain access. So either change the group ownership of the folder or set permissions to 777.
– Morbius1
May 2 '18 at 21:32
thx @Morbius1: that actually showed a 'good' group. solution came with the group of the parent/base folder (see below)
– vrms
May 3 '18 at 0:13
add a comment |
0
0
0
I have setup a samba server on 18.04 and run into a problem with access of sambashares
- user can access his home folder through samba (so I know the [samba]user exists, credentials are recognized)
- same user can not access any sambashare (even though user is in the group required, access rights are
774)
smb.conf looks like this:
[global]
workgroup = WORKGROUP
server string = %h server (Samba, Ubuntu)
dns proxy = no
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
panic action = /usr/share/samba/panic-action %d
server role = standalone server
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = no
passwd program = /usr/bin/passwd %u
passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
pam password change = yes
map to guest = bad user
#============== Share definitions =======================
[samba]
comment = Share for group Warehouse
path = /srv/smb/samba/
browseable = yes
writeable = yes
force create mode = 0660
force directory mode = 0660
Valid users = @sambausers
Any idea, what the root of this trouble may be?
samba
asked May 2 '18 at 13:37
vrmsvrms
96215
I have setup a samba server on 18.04 and run into a problem with access of sambashares
- user can access his home folder through samba (so I know the [samba]user exists, credentials are recognized)
- same user can not access any sambashare (even though user is in the group required, access rights are
774)
smb.conf looks like this:
[global]
workgroup = WORKGROUP
server string = %h server (Samba, Ubuntu)
dns proxy = no
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
panic action = /usr/share/samba/panic-action %d
server role = standalone server
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = no
passwd program = /usr/bin/passwd %u
passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
pam password change = yes
map to guest = bad user
#============== Share definitions =======================
[samba]
comment = Share for group Warehouse
path = /srv/smb/samba/
browseable = yes
writeable = yes
force create mode = 0660
force directory mode = 0660
Valid users = @sambausers
Any idea, what the root of this trouble may be?
samba
samba
asked May 2 '18 at 13:37
vrmsvrms
96215
asked May 2 '18 at 13:37
vrmsvrms
96215
edited May 2 '18 at 21:16
vrms
asked May 2 '18 at 13:37
vrmsvrms
96215
asked May 2 '18 at 13:37
vrmsvrms
96215
asked May 2 '18 at 13:37
vrmsvrms
96215
96215
bumped to the homepage by Community♦ 10 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 10 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Run "ls -dl /srv/smb/samba". What group is displayed? If it's not sambausers the remote user will not gain access. So either change the group ownership of the folder or set permissions to 777.
– Morbius1
May 2 '18 at 21:32
thx @Morbius1: that actually showed a 'good' group. solution came with the group of the parent/base folder (see below)
– vrms
May 3 '18 at 0:13
add a comment |
Run "ls -dl /srv/smb/samba". What group is displayed? If it's not sambausers the remote user will not gain access. So either change the group ownership of the folder or set permissions to 777.
– Morbius1
May 2 '18 at 21:32
thx @Morbius1: that actually showed a 'good' group. solution came with the group of the parent/base folder (see below)
– vrms
May 3 '18 at 0:13
Run "ls -dl /srv/smb/samba". What group is displayed? If it's not sambausers the remote user will not gain access. So either change the group ownership of the folder or set permissions to 777.
– Morbius1
May 2 '18 at 21:32
Run "ls -dl /srv/smb/samba". What group is displayed? If it's not sambausers the remote user will not gain access. So either change the group ownership of the folder or set permissions to 777.
– Morbius1
May 2 '18 at 21:32
thx @Morbius1: that actually showed a 'good' group. solution came with the group of the parent/base folder (see below)
– vrms
May 3 '18 at 0:13
thx @Morbius1: that actually showed a 'good' group. solution came with the group of the parent/base folder (see below)
– vrms
May 3 '18 at 0:13
add a comment |
1 Answer
1
active
oldest
votes
0
apparently the group of the parent folder of the share (/srv/smb in my case) does actually matter.
changing that to sambashare (which all my samba users are members off) fixed this issue.
answered May 2 '18 at 23:26
vrmsvrms
96215
Nope. What does matter is if members of the sambashare group can traverse the /srv/smb folder to get to the /samba folder. So regardless of the group of /srv/smb sambashare members would get access to /samba if the permissions of /srv/smb were 755, 775, 777, or even 711. But not 700, 770, or this curious 774 you are using since the "4" disables the traversal unless the group matches.
– Morbius1
May 3 '18 at 11:08
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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
});
}
});
draft saved
draft discarded
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%2faskubuntu.com%2fquestions%2f1031101%2fsamba-access-problem-18-04%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
0
apparently the group of the parent folder of the share (/srv/smb in my case) does actually matter.
changing that to sambashare (which all my samba users are members off) fixed this issue.
answered May 2 '18 at 23:26
vrmsvrms
96215
Nope. What does matter is if members of the sambashare group can traverse the /srv/smb folder to get to the /samba folder. So regardless of the group of /srv/smb sambashare members would get access to /samba if the permissions of /srv/smb were 755, 775, 777, or even 711. But not 700, 770, or this curious 774 you are using since the "4" disables the traversal unless the group matches.
– Morbius1
May 3 '18 at 11:08
add a comment |
0
apparently the group of the parent folder of the share (/srv/smb in my case) does actually matter.
changing that to sambashare (which all my samba users are members off) fixed this issue.
answered May 2 '18 at 23:26
vrmsvrms
96215
Nope. What does matter is if members of the sambashare group can traverse the /srv/smb folder to get to the /samba folder. So regardless of the group of /srv/smb sambashare members would get access to /samba if the permissions of /srv/smb were 755, 775, 777, or even 711. But not 700, 770, or this curious 774 you are using since the "4" disables the traversal unless the group matches.
– Morbius1
May 3 '18 at 11:08
add a comment |
0
0
0
apparently the group of the parent folder of the share (/srv/smb in my case) does actually matter.
changing that to sambashare (which all my samba users are members off) fixed this issue.
answered May 2 '18 at 23:26
vrmsvrms
96215
apparently the group of the parent folder of the share (/srv/smb in my case) does actually matter.
changing that to sambashare (which all my samba users are members off) fixed this issue.
answered May 2 '18 at 23:26
vrmsvrms
96215
answered May 2 '18 at 23:26
vrmsvrms
96215
answered May 2 '18 at 23:26
vrmsvrms
96215
answered May 2 '18 at 23:26
vrmsvrms
96215
96215
Nope. What does matter is if members of the sambashare group can traverse the /srv/smb folder to get to the /samba folder. So regardless of the group of /srv/smb sambashare members would get access to /samba if the permissions of /srv/smb were 755, 775, 777, or even 711. But not 700, 770, or this curious 774 you are using since the "4" disables the traversal unless the group matches.
– Morbius1
May 3 '18 at 11:08
add a comment |
Nope. What does matter is if members of the sambashare group can traverse the /srv/smb folder to get to the /samba folder. So regardless of the group of /srv/smb sambashare members would get access to /samba if the permissions of /srv/smb were 755, 775, 777, or even 711. But not 700, 770, or this curious 774 you are using since the "4" disables the traversal unless the group matches.
– Morbius1
May 3 '18 at 11:08
Nope. What does matter is if members of the sambashare group can traverse the /srv/smb folder to get to the /samba folder. So regardless of the group of /srv/smb sambashare members would get access to /samba if the permissions of /srv/smb were 755, 775, 777, or even 711. But not 700, 770, or this curious 774 you are using since the "4" disables the traversal unless the group matches.
– Morbius1
May 3 '18 at 11:08
Nope. What does matter is if members of the sambashare group can traverse the /srv/smb folder to get to the /samba folder. So regardless of the group of /srv/smb sambashare members would get access to /samba if the permissions of /srv/smb were 755, 775, 777, or even 711. But not 700, 770, or this curious 774 you are using since the "4" disables the traversal unless the group matches.
– Morbius1
May 3 '18 at 11:08
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- 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.
draft saved
draft discarded
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%2faskubuntu.com%2fquestions%2f1031101%2fsamba-access-problem-18-04%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
Run "ls -dl /srv/smb/samba". What group is displayed? If it's not sambausers the remote user will not gain access. So either change the group ownership of the folder or set permissions to 777.
– Morbius1
May 2 '18 at 21:32
thx @Morbius1: that actually showed a 'good' group. solution came with the group of the parent/base folder (see below)
– vrms
May 3 '18 at 0:13