Filesharing and Linux Mint 20.1 Ulyssa (Cinnamon Ed.)

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
cdawe
Level 1
Level 1
Posts: 17
Joined: Sun Jul 27, 2014 2:39 pm

Filesharing and Linux Mint 20.1 Ulyssa (Cinnamon Ed.)

Post by cdawe »

Hi folks,

I've installed the latest version of Linux Mint 20.1 Ulyssa (Cinnamon Edition) and I was looking to setting up sharing of a number of drives to back up things between my Windows 10 Pro Boxes and the Mint Box.

Having had experience with SAMBA in the past, I proceeded to install it. I attempted to get sharing working by using the share option which appeared in the right click menu, but no go. I hit the wall that one can only share one's own files error. As indicated in the forum elsewhere, I made a few changes to the smb.conf file, for example, adding in the "usershare owner only = false" setting, etc. Then there were errors regarding the system not being able to convert Everyone to a SID, etc. Made a few more changes to the configuration file. LOL! :lol:

Anyways, I still, can't achieve Linux Mint "file sharing joy" with that menu option. Even with the configuration of SAMBA from the smb.conf file, nothing is really behaving as I want. I did one setup that one user suggested here, but that appeared to just open the shares up willy nilly, with no password challenges at all, etc. Not ideal. I want to have my Windows 10 Pro users (my brother and I) to be able to connect to the shares on the Mint box, be challenged for their password to the share via SAMBA system, and if OK, connect and go about the backing up process.

Guys, in a spirit of transparency, is there any desire of the Mint 20.1 leaders, here in the community, to support this kind of idea, or is there really no true interest in building in support for anyone out here in the "wild" to be able to share in the mixed environment like I have? I see decreasing support for this as the distribution numbers climb ahead. I love Linux, Windows NT and MacOS. Why should we have to choose? :D

In any event, I've included the smb.conf file for your perusal, tearing apart ... and hopeful, apreciated-in-advance help in making my little computer boxes happy and backed up ... like every sensible human should. :wink:

Code: Select all

# 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]
usershare owner only = false
client max protocol = NT1
;client ipc signing = auto
dns proxy = no

## Browsing/Identification ###
   force group = sambashare

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

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

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


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

#======================= 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 = 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
# 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/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
Can anyone help me solve this? What other steps must I do.

Thanks to all the developers in any event, this is the cleanest looking version I've seen yet. Generally very user-focused and refined. Good work, indeed!

I await your learned replies. :D

Curt
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
altair4
Level 20
Level 20
Posts: 11458
Joined: Tue Feb 03, 2009 10:27 am

Re: Filesharing and Linux Mint 20.1 Ulyssa (Cinnamon Ed.)

Post by altair4 »

I attempted to get sharing working by using the share option which appeared in the right click menu, but no go. I hit the wall that one can only share one's own files error.
It's not an error. It was designed to do that: Prevent an ordinary user from creating a share of something he doesn't own.
Then there were errors regarding the system not being able to convert Everyone to a SID, etc.
Was this the error:
ns-sid.png
ns-sid.png (7.33 KiB) Viewed 348 times
That's because of this line in your smb..conf: client max protocol = NT1
Remove it and restart smbd.

You can't have the max protocol level be lower than the min.

Took a fresh Mint Cinnamon 20 machine, created a nemo-share ( samba usershare ) of my Public folder, and connected to the machine from Win10:
Win10-to-Mint20.png
Took me less than 5 minutes to set this up.

Now ... mind you ... I'm running Win10 the way Microsoft wants me to run it - with SMBv1 disabled. So I cant go to Explorer > Network and expect it to magically discover any of my Linux machines so I have to address the machine explicitly.

Some light reading:

Samba and Mint20: viewtopic.php?f=42&t=322404

Windows 10 and Samba File Sharing: viewtopic.php?f=42&t=199907
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Locked

Return to “Networking”