Zugriff auf SAMBA-Shares nur für einen User möglich

[Hadan_P]

Grüß euch!

Gleich mal vorweg, ich weiß dass es gleich unter mir einen Thread mit einem ähnlichen Problem gibt, meines ist aber imho anders genug um einen neuen Thread zu rechtfertigen.

Ausgangsposition:
Ich habe hier einen neuen Server der hauptsächlich als NAS arbeitet. Als OS läuft Linux Mint 15.
Die Shares werden per Samba zur Verfügung gestellt.
4 Clients sollen auf die Shares zugreifen, 3 laufen auf Win7, das Tablet auf Android 4.2.
Alle Geräte befinden sich in der gleichen Arbeitsgruppe, sehen sich untereinander & können sich auch pingen.
Eine Info noch: "stucks" bin ich, dieser Zugang wird auf meinem Rechner verwendet & ist auch der Hauptuser am Server

Ich habe am Server alle User, die Zugriff haben sollen, sowohl als Unix-User, als auch als Samba-User angelegt. Username/Passwort ist für Unix & Samba jeweils gleich & deckt sich auch mit dem Windows-Anmeldedaten.

Jetzt zum Problem:
Ich kann auf meinem Rechner ohne Probleme alle Shares verbinden & auch darauf zugreifen (read/write).
Versuche ich das gleiche z.b. am HTPC (User "llano"), wird zwar der Share als Netzlaufwerk verbunden, will ich dann darauf zugreifen, kommt eine Fehlermeldung:

Das gleiche auf dem Laptop meiner Freundin (User "kathi").
Gleiches Verhalten habe ich wenn ich im Explorer über "Netzwerk" gehe: Ich sehe den Server & die Freigaben, klicke ich dann drauf kommt eine Fehlermeldung.

Problem im Windows traue ich mich fast auszuschließen, da ich auf dem HTPC auf die Shares zugreifen kann wenn ich diese mit den Anmeldedaten meines Users verbinde.
Verwende ich die Daten von "llano", bekomme ich auch auf meinem PC die obige Fehlermeldung.

Hier mal meine Samba-Config:

#======================= Global Settings =======================

[global]

## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
	workgroup = webgasse

# server string is the equivalent of the NT Description field
	server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
	dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
;   name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes

#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
	log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
	max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
	syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
	panic action = /usr/share/samba/panic-action %d

####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
#   security = user

# You may wish to use password encryption.  See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
;	encrypt passwords = yes

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
;	passdb backend = tdbsam

	obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
	unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
	passwd program = /usr/bin/passwd %u
	passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
	pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
	map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
;   domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
#         SO_RCVBUF=8192 SO_SNDBUF=8192
#   socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
#   domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
;   winbind enum groups = yes
;   winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;	usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
	usershare allow guests = yes
	security = user
;	guest ok = no
;	guest account = nobody
	username map = /etc/samba/smbusers

#======================= Share Definitions =======================
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each 
# user's home director as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# The following parameter makes sure that only "username" can connect
#
# This might need tweaking when using external authentication schemes
;   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[data]
	comment = Documents, Software
	path = /media/stucks/Multimedia/data
	writeable = yes
;	browseable = yes
	valid users = android, kathi, llano, stucks

[documentary]
	path = /media/stucks/Multimedia/documentary
	writeable = yes
;	browseable = yes
	valid users = android, kathi, llano, stucks

[Fotos]
	path = /media/stucks/Multimedia/Fotos
	writeable = yes
;	browseable = yes
	valid users = android, kathi, llano, stucks

[game_data]
	comment = Games, Saves, Tools
	path = /media/stucks/Multimedia/game_data
	writeable = yes
;	browseable = yes
	valid users = android, kathi, llano, stucks

[HTPC]
	path = /media/stucks/Multimedia/HTPC
	writeable = yes
;	browseable = yes
	valid users = llano, stucks

[movies]
	comment = Movies, Cartoon Shorts
	path = /media/stucks/Multimedia/movies
	writeable = yes
;	browseable = yes
	valid users = android, kathi, llano, stucks

[series]
	path = /media/stucks/Multimedia/series
	writeable = yes
;	browseable = yes
	valid users = android, kathi, llano, stucks

[backup]
	comment = Backups
	path = /media/stucks/Multimedia/Privat
	writeable = yes
	browseable = no
	valid users = android, kathi, llano, stucks

[stucks]
	path = /media/stucks/Multimedia/stucks
	writeable = yes
	browseable = no
	valid users = android, llano, stucks

[torrents]
	path = /home/stucks/Downloads
	writeable = yes
	browseable = no
	valid users = stucks

&hier die Samba-User:

stucks = stucks
android = android
kathi = kathi
llano = llano

Hatte die Vermutung, dass es eventuell mit den Zugriffsrechten der Linux-User zu tun hat (eigentlich glaub ich noch immer dass es dait was zu tun hat, aber komm nicht dahinter was genau das Problem ist)
Die Ordner gehörten "stucks" der Gruppe "stucks".
Habe zuerst eine neue Gruppe "samba" angelegt, die 4 User dieser Gruppe zugeordnet & die Verzeichnisse auch dieser Gruppe gegeben.
Nachdem dass auch nichts gebracht hat habe ich den Holzhammer ausgepackt & die ganzen Ordnerechte auf 777 gesetzt, auch ohne Erfolg.
So sehen die Ordner aus:

drwxrwxrwx 17 stucks samba  4096 Aug 31 12:32 data
drwxrwxrwx 10 stucks samba  4096 Jun 29 14:12 documentary
drwxrwxrwx 37 stucks samba  4096 Jun 29 14:12 Fotos
drwxrwxrwx 10 stucks samba  4096 Sep 20 10:51 game_data
drwxrwxrwx  7 stucks samba  4096 Jul  7 07:13 HTPC
drwxrwxrwx  2 root   samba 16384 Sep 21 12:31 lost+found
drwxrwxrwx  3 stucks samba  4096 Aug  4 23:00 movies
drwxrwxrwx 85 stucks samba  4096 Jun 30 14:28 music
drwxrwxrwx  9 stucks samba  4096 Sep  1 19:50 Privat
drwxrwxrwx 32 stucks samba  4096 Aug 27 22:31 series
drwxrwxrwx 14 stucks samba  4096 Sep 19 17:54 stucks

Die Samba-Logs hab ich kontrolliert, da sehe ich nicht wirklich was.

Irgendwer eine Idee was ich übersehe?

mfg
Hadan

 

[Hadan_P]

Ein User im offiziellen Linux-Mint Forum hat das Problem gelöst, hier eine Übersetzung seiner Antwort, hilft vielleicht irgendwann irgendwem:
-------------------------------------------
Das Problem ist dass alle Verzeichnisse die geshared werden unter /media/stucks liegen.
Da /media/stucks vom System generiert wurde werden alle Berechtigungsänderungen vom System überschrieben.

Ein Ausweg ist, alle Remote-Users als "stucks" erscheinen zu lassen. Folgende Änderung muss in smb.conf gemacht werden:

[data]
comment = Documents, Software
path = /media/stucks/Multimedia/data
writeable = yes
; browseable = yes
force user = stucks
valid users = android, kathi, llano, stucks

Das sieht ein wenig seltsam aus, da "force user" "valid users" zu wiedersprechen scheint. Was hier aber passiert ist, dass Samba den Zugriff auf die "valid users" beschränkt, sobald diese eingeloggt sind, werden sie aber zum "forced user" konvertiert.
Alles was sie dann im System machen erscheint als ob "forced user" es tut.

Nach den Änderungen an der conf Samba neu starten:

sudo service smbd restart

------------------------------------------

mfg
Hadan