Friday, May 3, 2024
 Popular · Latest · Hot · Upcoming
1
rated 0 times [  1] [ 0]  / answers: 1 / hits: 10351  / 2 Years ago, thu, march 31, 2022, 12:14:10

I have a Samba related problem.



I have a successful samba server set up on my home server. Unfortunately only my account can access the shares when force user is not set to my account (server). I cannot understand why the other user cannot access my share "Vector_Public" when I haven't set "force user = server". Do you have any ideas to what might cause this? I'm a Samba noob so please if I've misunderstood any of the settings:



[Vector_Public]
comment = Vector public share
read only = no
path = /media/Storage/Public
guest ok = no
force user = server
force group = storage_public
create mask = 0770
directory mask = 0770
security mask = 0770
force create mode = 0770
force directory mode = 0770
valid users = server storage_share
browseable = yes
writeable = yes
vfs objects = recycle
recycle:repository = .deleted/%U
recycle:keeptree = yes
recycle:touch = yes
recycle:versions = yes
recycle:maxsize = 0

[Vector_Private]
comment = Vector private share (Niklas)
read only = no
path = /media/Storage/Private
guest ok = no
force user = server
force group = server
create mask = 0770
directory mask = 0770
security mask = 0770
force create mode = 0770
force directory mode = 0770
valid users = server
browseable = yes
writeable = yes
vfs objects = recycle
recycle:repository = .deleted/%U
recycle:keeptree = yes
recycle:touch = yes
recycle:versions = yes
recycle:maxsize = 0


The permissions on the two directories are:



drwx------ 6 server server 4096 2011-10-05 20:40 Private
drwxrwx--- 5 server storage_public 4096 2011-10-05 20:28 Public


It's the directory Public that I have this problem on.



Apparently none of the settings under the share Vector_Public changes this behaviour so it must be because of some other setting, these are all the other settings in my config:



   workgroup = ROSENQVIST
server string = %h server (Samba, Ubuntu)
# wins support = no
; wins server = w.x.y.z
dns proxy = no
; name resolve order = lmhosts host wins bcast
; interfaces = 127.0.0.0/8 eth0
; bind interfaces only = yes
log file = /var/log/samba/log.%m
max log size = 1000
# syslog only = no
syslog = 0
panic action = /usr/share/samba/panic-action %d
security = user
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = yes
passwd program = /usr/bin/passwd %u
passwd chat = *Entersnews*spassword:* %n
*Retypesnews*spassword:* %n
*passwordsupdatedssuccessfully* .
pam password change = yes
map to guest = bad user
; domain logons = yes
; logon path = %Nprofiles%U
# logon path = %N%Uprofile
; logon drive = H:
# logon home = %N%U
; logon script = logon.cmd
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
; add group script = /usr/sbin/addgroup --force-badname %g
; printing = bsd
; printcap name = /etc/printcap
; printing = cups
; printcap name = cups
; include = /home/samba/etc/smb.conf.%m
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
; winbind enum groups = yes
; winbind enum users = yes
; usershare max shares = 100
usershare allow guests = no


Any ideas what I should do? (please also check the new comments)



Additionally, how do I know if my network have WINS server support?


More From » samba

 Answers
5

The problem was because of an issue with flow of permissions. Everything worked when I changed the parent directory's (to the directories that were shared) permissions to allow reading for other users.


[#43199] Saturday, April 2, 2022, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
nquirewha

Total Points: 256
Total Questions: 109
Total Answers: 122

Location: Namibia
Member since Mon, Feb 21, 2022
2 Years ago
nquirewha questions
Wed, Jan 26, 22, 03:38, 2 Years ago
Mon, Nov 1, 21, 13:50, 3 Years ago
Thu, Dec 1, 22, 09:23, 1 Year ago
;