realShadowhunter at gmx.net
2019-May-17  17:26 UTC
[Samba] Moving home directories to another location leads to NT_STATUS_ACCESS_DENIED listing
of course
 
my smb.conf
 
 
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 
 
#======================= Global Settings ====================== 
[global]
os level = 20
obey pam restrictions = yes
passwd program = /usr/bin/passwd %u
unix password sync = yes
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n
*password\supdated\ssuccessfully* .
panic action = /usr/share/samba/panic-action %d
passdb backend = tdbsam
workgroup = PRIVAT
pam password change = yes
map to guest = bad user
socket options = TCP_NODELAY
dns proxy = no
server role = standalone server
log file = /var/log/samba/log.%m
max log size = 1000
usershare allow guests = yes
syslog = 0
    
 
## Browsing/Identification ###
 
# Change this to the workgroup/NT-domain name your Samba server will part of
 
# 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.
 
#### 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
 
# Cap the size of the individual log files (in KiB).
 
# 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.
 
# Do something sensible when Samba crashes: mail the admin a backtrace
 
 
####### Authentication #######
 
# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server",
"classic primary
# domain controller", "classic backup domain controller",
"active
# directory domain controller". 
#
# Most people will want "standalone sever" or "member
server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
 
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
 
 
# 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.
 
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan at
informatik.tu-muenchen.de[mailto:%20kahan at informatik.tu-muenchen.de]> for
# sending the correct chat script for the passwd program in Debian Sarge).
 
# 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'.
 
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
 
########## Domains ###########
 
#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain
controller'
# or '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
 
# 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
 
# 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
 
#======================= Share Definitions ====================== 
 
[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700
 
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin
 
 
 
[Miscellaneous]
writeable = yes
valid users = user1
path = /mnt/volume6
 
[homes]
writeable = yes
valid users = user1,user2
write list = user1,user2
 
 
The smb.conf is pretty much all standard except I synchronize with system users.
 
The partitions are mounted on /mnt/volume1 through volume6. These volumes are
added into the FSTAB
 
 
/dev/md0 /mnt/volume1 ext4 defaults,nofail,discard 0 0
 
Every mount works fine just the homes one doesn't want to comply :-)
 >Can we see your smb.conf ?
>Can you also tell us how you are mounting the volume ?
Rowland
Rowland penny
2019-May-17  17:47 UTC
[Samba] Moving home directories to another location leads to NT_STATUS_ACCESS_DENIED listing
On 17/05/2019 18:26, realShadowhunter at gmx.net wrote> [global] > os level = 20 > obey pam restrictions = yes > passwd program = /usr/bin/passwd %u > unix password sync = yes > passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . > panic action = /usr/share/samba/panic-action %d > workgroup = PRIVAT > pam password change = yes > map to guest = bad user > socket options = TCP_NODELAY > dns proxy = no > server role = standalone server > log file = /var/log/samba/log.%m > max log size = 1000 > usershare allow guests = yes > syslog = 0 > > [printers] > comment = All Printers > browseable = no > path = /var/spool/samba > printable = yes > create mask = 0700 > > [print$] > comment = Printer Drivers > path = /var/lib/samba/printers > > [Miscellaneous] > writeable = yes > valid users = user1 > path = /mnt/volume6 > > [homes] > writeable = yes > valid users = user1,user2 > write list = user1,user2 > > The smb.conf is pretty much all standard except I synchronize with system users.Well you would have to, what with it being a 'standalone server' ;-)> The partitions are mounted on /mnt/volume1 through volume6. These volumes are added into the FSTAB > > > /dev/md0 /mnt/volume1 ext4 defaults,nofail,discard 0 0 > > Every mount works fine just the homes one doesn't want to comply :-) >Well it probably wouldn't, unless you are connecting as 'user1' or 'user2', they are the only users that will be allowed access. I would have expected some thing like this: [homes] comment = Home Directories browseable = no read only = no create mask = 0700 directory mask = 0700 valid users = %S You would also have to set the users homedir in /etc/passwd and Samba. Rowland
Seemingly Similar Threads
- Moving home directories to another location leads to NT_STATUS_ACCESS_DENIED listing
 - Moving home directories to another location leads to NT_STATUS_ACCESS_DENIED listing
 - Moving home directories to another location leads to NT_STATUS_ACCESS_DENIED listing
 - Moving home directories to another location leads to NT_STATUS_ACCESS_DENIED listing
 - certain users can't map home directories