Samba share issues need help

Struggling to get my dietpi_userdata availble over samba so I can copy files to and from it. I installed the samba server client from the dietpi software tool and its running but I only access the user directory for dietpi user. How do I get to see dietpi_user_data instead, I thought this was set up by default? Looking at the smb.conf file i cant fathom out what bit to edit. Sorry but this has me too confused.

I am not samba expert but at the bottom of the /etc/samba/smb.conf file you should be able to put a path to whatever you want to export. Mine looks like below as I am sharing the /mnt/raid folder. Specifically the line path = /mnt/raid
I thought what you wanted was the actual default when I first fired samba up.

[dietpi]
	comment = DietPi Share
	path = /mnt/raid
	browseable = yes
	create mask = 0664
	directory mask = 0775
	valid users = dietpi
	writeable = yes
max connections = 12

Default should be /mnt/dietpi_userdata/

@TheCrystalGipsy can you share your configuration file

cat /etc/samba/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]

## Browsing/Identification ###

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

#### 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

# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
   logging = file

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


####### 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 server" 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.
   server role = standalone server

   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 ###########

#
# The following settings only takes effect if 'server role = classic
# primary domain controller', 'server role = classic 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/useradd --create-home %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 config * :              backend = tdb
;   idmap config * :              range   = 3000-7999
;   idmap config YOURDOMAINHERE : backend = tdb
;   idmap config YOURDOMAINHERE : range   = 100000-999999
;   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 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

#======================= Share Definitions =======================

[homes]
   comment = Home Directories
   browseable = yes

# 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 = no

# 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 = 0775

# 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 = 0775

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# 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

[printers]
   comment = All Printers
   browseable = no
   path = /var/tmp
   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

ok same as this one. New build: Can't access external HD - #26 by Joulinar

[quote=“anika200, post:2, topic:19224”]

Thanks added this at end and changed the directory it works.

Looks like the default ones borked since the update to v9 as this is a new install this week.

This is not true. Your configuration is fare away from our default. You are using the Samba own configuration and not a DietPi one. I linked a post above where you can find a solution switching to DietPi default

This is our smb.conf DietPi/.conf/dps_96/conf at 6a4b6e0486ffe363f6f75fda6f6d3718ac6aa627 · MichaIng/DietPi · GitHub
It’s same since 4 years and has been changed last time on v6.31

I installed it via Dietpit-Software so why doesnt it use your config?

For this we would need the whole log from your SMB server installation. At least I’m not able to replicate the behaviour. For me configuration is downloaded correctly as it should.

I guess you had samba already installed before, and maybe purged it, but not the old config file, which is preserved on an new installation via dietpi-software.
From the installation script:

Maybe a better approach would be to backup the old config and install the dietpi-one to stay in line with our docs?!

Its a brand new install, all software was installed via dietpi-software installer. So not sure how that could happen. Anyway its working now as I wanted so all good.

Look at the script, the code does not lie :slight_smile:

If the file /etc/samba/smb.conf already exists it will not be overwritten with our config.
It was also a completly fresh DietPi installation?
Maybe you installed it somewhen in the past with some other software together, as a dependency :thinking:

did you install SMB server alone or together with some other software at the same time?

I installed Roon and Plex first, using dietpi-software tool, but they dont install the server bit only the regular smb for network shares but maybe they do? I then installed samba server using diet-pi software tool. It was not showing as installed before this.

ok it seems to be the samba client installation, as installation of smb client will create configuration file /etc/samba/smb.conf already. Of course this hinders the download of the conf file during the installation of the SAMBA server

Indeed, i made a installation on my testsystem:

CLI output of installation
[ INFO ] DietPi-Software | APT install cifs-utils smbclient, please wait...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libarchive13 libavahi-client3 libavahi-common-data libavahi-common3 libicu72
  libldb2 liblmdb0 libsmbclient libtalloc2 libtdb1 libtevent0 libwbclient0
  libxml2 samba-common samba-libs ucf
Suggested packages:
  winbind lrzip heimdal-clients
Recommended packages:
  keyutils samba-common-bin
The following NEW packages will be installed:
  cifs-utils libarchive13 libavahi-client3 libavahi-common-data
  libavahi-common3 libicu72 libldb2 liblmdb0 libsmbclient libtalloc2 libtdb1
  libtevent0 libwbclient0 libxml2 samba-common samba-libs smbclient ucf
0 upgraded, 18 newly installed, 0 to remove and 0 not upgraded.
Need to get 16.7 MB of archives.
After this operation, 76.8 MB of additional disk space will be used

I think the culprit is samba-common.
@MichaIng Should we adress this in the installation script somehow?

We could pre-create configuration file, similar to server installation.

Ah, so when the Samba client is installed as well or was previously, or an SMB mount was added via dietpi-drive_manager. Strange that a Samba server config file is shipped with a package shared between server and client, instead of with the server only.

However, the file is actually coming from /usr/share/samba/smb.conf, so we can check whether /etc/samba/smb.conf is the same, if it exists, to decide whether to install our config.

EDIT: Fixed with: v9.1 · MichaIng/DietPi@8139155 · GitHub

2 Likes