At least some of the structure looks as if it’s got mixed up, items from share definitions are mixed with items from or for other sections.
Have you run the Samba’s associated parameter checking utility testparm on your configuration file while attempting connections to the shares through it?
Thanks again. When I ran testparm (which sounds to me like a fun job taste-testing Parmesan cheese), I got this:
Load smb config files from /etc/samba/smb.conf
lpcfg_do_global_parameter: WARNING: The "encrypt passwords" option is deprecated
Unknown parameter encountered: "server smb encrypt"
Ignoring unknown parameter "server smb encrypt"
Unknown parameter encountered: "client smb encrypt"
Ignoring unknown parameter "client smb encrypt"
Loaded services file OK.
Weak crypto is allowed
Server role: ROLE_STANDALONE
But, based on the documentation you sent, what I have in my config looks right. (The documentation did say default instead of required, but neither one seems to work.)
server min protocol = SMB3_11
server smb encrypt = required
server signing = required
client min protocol = SMB3_11
client smb encrypt = required
client signing = required
So, any more thoughts?
When I looked at the config file there seemed to be entries that could have been used when defining a Samba share for the media share. But they were in the global section, these can potentially be not helping with your inaccessible Samba share. You may need to restore a backup of the samba config file, then re-add the samba SMB 3.11 entry, client server signing and/or client server encryption.
Afterwards using the GUI only then re-create the share definition along with configuring the other shares.
Argh, this is still not working.
Here’s the config file now after following your instructions about rebuilding the share.
#
# 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
logging = file
workgroup = WORKGROUP
map to guest = bad user
obey pam restrictions = yes
username map = /etc/samba/user.map
pam password change = yes
netbios name = Debian
usershare allow guests = yes
log file = /var/log/samba/log.%m
allow hosts = all
encrypt passwords = yes
valid users = danieladougan,root,sync,mediagiant
unix password sync = yes
writeable = yes
auto services = media
server role = standalone server
path = /media
max log size = 1000
panic action = /usr/share/samba/panic-action %d
server min protocol = SMB3_11
server smb encrypt = required
server signing = required
client min protocol = SMB3_11
client smb encrypt = required
client signing = required
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
#### 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).
# 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.
# 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 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.
# 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@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 = 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/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 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
#======================= Share Definitions =======================
[homes]
comment = Home Directories
directory mask = 0700
writeable = yes
valid users = danieladougan
create mask = 0700
# 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.
# 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.
# 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.
# 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
# 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/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
[media]
write list = mediagiant,danieladougan
user = mediagiant,danieladougan
Here’s testparm now:
> testparm
Load smb config files from /etc/samba/smb.conf
lpcfg_do_global_parameter: WARNING: The "encrypt passwords" option is deprecated
Unknown parameter encountered: "server smb encrypt"
Ignoring unknown parameter "server smb encrypt"
Unknown parameter encountered: "client smb encrypt"
Ignoring unknown parameter "client smb encrypt"
Unknown parameter encountered: "user"
Ignoring unknown parameter "user"
Loaded services file OK.
Weak crypto is allowed
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
auto services = media
client min protocol = SMB3
client signing = required
log file = /var/log/samba/log.%m
logging = file
map to guest = Bad User
max log size = 1000
obey pam restrictions = Yes
pam password change = Yes
panic action = /usr/share/samba/panic-action %d
server min protocol = SMB3
server role = standalone server
server signing = required
unix password sync = Yes
username map = /etc/samba/user.map
usershare allow guests = Yes
idmap config * : backend = tdb
hosts allow = all
path = /media
valid users = danieladougan root sync mediagiant
[homes]
comment = Home Directories
create mask = 0700
directory mask = 0700
valid users = danieladougan
[printers]
browseable = No
comment = All Printers
create mask = 0700
path = /var/spool/samba
printable = Yes
read only = Yes
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
read only = Yes
[media]
write list = mediagiant danieladougan
I thought someone recommended something like this but I don’t see the post now?
Before I ever installed Debian and Webmin on this box, I tried to install OMV. I got critical errors on installation.
What were the errors? I don’t remember. It has been three years. I was just desperate for any OS that would work AT ALL.
I got OMV to work on my Raspberry Pi 3B+ before that, but the hardware limitations of the Pi made it unreliable.
Maybe there was some hardware compatibility issue with my Buffalo TeraStation that prevented it from installing?
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.