LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)
-   -   Mint Not Saving Samba Sharing Settings After Restart/Shutdown (https://www.linuxquestions.org/questions/linux-server-73/mint-not-saving-samba-sharing-settings-after-restart-shutdown-4175622808/)

Oblivious700 01-31-2018 03:39 PM

Mint Not Saving Samba Sharing Settings After Restart/Shutdown
 
I pieced this PC together cheaply in December for a small home file server/HTPC. I wanted to dabble in Linux since i'm an IT major in school but I don't have much experience with Linux. I first tried Ubuntu and it was a nightmare. I had so many issues with it I switch to Linux Mint. But I’m presented with a different problem. Everything is set-up correctly except for when I turn off the system or do a restart the samba shares settings are gone and I have to go back and share the folders again. I've tried working with the SMB.conf file but the problem still persists. Does anyone have any ideas about this? I will attach the smb.conf file so you guys can look it over.

Code:

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

[global]

## Browsing/Identification ###

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

# 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

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

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

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

#
# 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
        usershare allow guests = yes

#======================= 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 directory 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 = 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.
# Un-comment the following parameter to make 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 = yes
        browseable = yes
        create mask = 0600
        directory mask = 0700

[Media]
    comment = Samba Sharing
    path = /media/bryon/Media
    read only = no   
    writeable = yes   
    guest ok = yes   
    browseable = yes
    create mask = 0777
    directory mask = 0777
   


[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, @bryon


sixerjman 02-01-2018 10:43 AM

'smbclient -gNL hostname ' will list available shares on the host. Do you have the correct permissions on the /media folder? I use Debian and Fedora, and on both of those distributions the /media directory is owned by root:root and not writable by non-root users. Also, is the shared folder on a CDROM or other external medium that may not be mounted at the time samba initializes?

Oblivious700 02-01-2018 06:16 PM

2 Attachment(s)
Quote:

Originally Posted by sixerjman (Post 5814296)
'smbclient -gNL hostname ' will list available shares on the host. Do you have the correct permissions on the /media folder? I use Debian and Fedora, and on both of those distributions the /media directory is owned by root:root and not writable by non-root users. Also, is the shared folder on a CDROM or other external medium that may not be mounted at the time samba initializes?

This is what is listed when I typed 'smbclient -gNL hostname in a terminal.

Attachment 26883

Here is a screenshot of the permissions of the folder I'm trying to share.

Attachment 26884

To answer you're final concern, the folder is located on a secondary hard drive. Mint is installed and running off of an SSD and the folder I'm wanting to share is on another HDD installed on the system. If I share a folder that is on the SSD then it's working perfect, shows up on my network to other PC's but if it's a folder on the secondary storage drive then it's all kinds of problems.

username_11011 02-03-2018 09:29 AM

Meh-- I know what *I* would do. But, it's a hack. I would set up an smb.conf the way I want it and store it somewhere. Then, I would add a script to the startup procedure that copies the script to /etc/samba and restarts the samba daemon. Like this:

Code:

cp <path>/smb.conf /etc/samba
/etc/init.d/samba restart


michaelk 02-03-2018 09:57 AM

You need to use the actual hostname of the computer and not the literal word "hostname" On the same computer you can also use localhost.

smblient -NL localhost

What do you mean by the settings are gone? Are the shares visible but not accessible?

force user = Bryon is only valid for shares and not as a global directive. Your share Media
Quote:

[Media]
comment = Samba Sharing
path = /media/bryon/Media
read only = no
writeable = yes
guest ok = yes
browseable = yes
create mask = 0777
directory mask = 0777
Should be working and accessible if the directory permissions are set correctly. Shares created using Nautilus are called usershares versus those that are directly defined in the smb.conf file. They are saved in a different directory (/var/locks/usershares). I assume that on boot up samba is not configuring them correctly.

Oblivious700 02-05-2018 12:42 PM

2 Attachment(s)
Quote:

Originally Posted by michaelk (Post 5815290)
You need to use the actual hostname of the computer and not the literal word "hostname" On the same computer you can also use localhost.

smblient -NL localhost

What do you mean by the settings are gone? Are the shares visible but not accessible?

force user = Bryon is only valid for shares and not as a global directive. Your share Media

Should be working and accessible if the directory permissions are set correctly. Shares created using Nautilus are called usershares versus those that are directly defined in the smb.conf file. They are saved in a different directory (/var/locks/usershares). I assume that on boot up samba is not configuring them correctly.

Attachment 26919

Here is what I got from using localhost with smbclient.

Attachment 26920

Whenever I restart or turn the server on this is what happens to my share settings. They are reset to not be on. I have to go into properties and reshare everything again.

Oblivious700 02-08-2018 11:10 AM

Any have ideas on why my system will keep keep the shared folder settings?


All times are GMT -5. The time now is 11:51 PM.