how to create SMB folder requiring authentication

[stimpe]

I have a samba share called Video, allowing users(guests) on my network to dump movies, etc into. I was wondering how I could create another share/folder requiring authentication while still allowing guest access for Video?

[altair4]

I honestly don't know how to answer your question.

I mean, go though the same process you used to create the guest share and then make another one that does not allow guest access. You will have to create users on your server corresponding to the client users and add them to the samba password database.

Once you create the user you can add them to the samba database with this command:

Code: Select all

sudo smbpasswd -a client-user-name

You didn't tell us the following information so it's hard to be specific:

What version of Mint you are using.
What is you Desktop Environment: Cinnamon, MATE, XFCE?
How did you create the current guest share: Through Nautilus / Nemo or by creating a share in smb.conf directly?

[stimpe]

sorry, here is the information you asked

What version of Mint you are using. - mint 14
What is you Desktop Environment: Cinnamon, MATE, XFCE? - KDE
How did you create the current guest share: Through Nautilus / Nemo or by creating a share in smb.conf directly? -SMB.CONF

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. 
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

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

[global]

## Browsing/Identification ###

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

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

# 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

# What naming service and in what order should we use to resolve host names
# to IP addresses
;   name resolve order = lmhosts host wins bcast

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

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
;	security = user

# You may wish to use password encryption.  See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
;	encrypt passwords = yes

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

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
;   domain logons = yes
#
# The following setting only takes effect if '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

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
#   load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
;   printing = bsd
;   printcap name = /etc/printcap

# CUPS printing.  See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
;	printing = cups
;   printcap name = cups

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

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
#         SO_RCVBUF=8192 SO_SNDBUF=8192
#   socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
#   domain master = auto

# 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

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
;   winbind enum groups = yes
;   winbind enum users = yes

# 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 director 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
# The following parameter makes sure that only "username" can connect
#
# 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

	server role = domain controller
	username map = /etc/samba/smbusers
	security = user
	guest ok = yes
[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

# A sample share for sharing your CD-ROM with others.
;[cdrom]
;   comment = Samba server's CD-ROM
;   read only = yes
;   locking = no
;   path = /cdrom
;   guest ok = yes

# The next two parameters show how to auto-mount a CD-ROM when the
#	cdrom share is accesed. For this to work /etc/fstab must contain
#	an entry like this:
#
#       /dev/scd0   /cdrom  iso9660 defaults,noauto,ro,user   0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
#	is mounted on /cdrom
#
;   preexec = /bin/mount /cdrom
;   postexec = /bin/umount /cdrom

[sysvol]
	path = /var/lib/samba/sysvol
	read only = no

[netlogon]
	path = /var/lib/samba/sysvol/localdomain/scripts
	read only = no

[Video]
	path = /home/server/Videos
;	writeable = no
	browseable = yes
	guest ok = yes
	public = yes
	read only = no
	writeable = yes
	
[LandonBackup]
	path = /home/landon/Backup
	browseable = yes
	guest ok = no
	public = yes
	read only = no
	writeable = yes

I have created a user account named 'landon'. now how do i make it authenticate a user once they try and access that share?

[altair4]

I'm guessing you're talking about this share:

[LandonBackup]
path = /home/landon/Backup
browseable = yes
guest ok = no
public = yes
read only = no
writeable = yes

Samba will read the share definition sequentially line by line. "guest ok = no" will require the samba client to authenticate to gain access. "public = yes" is synonymous to "guest ok = yes" so it turns it on again resulting in anybody gaining access. Remove the "public" line so the share looks like this:

[LandonBackup]
path = /home/landon/Backup
browseable = yes
guest ok = no
read only = no
writeable = yes

Then restart samba:

Code: Select all

sudo service smbd restart

Then make sure landon is in the samba password database:

Code: Select all

sudo smbpasswd -a landon

Note: you do have one anomaly in your smb.conf and that's this:

;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

server role = domain controller
username map = /etc/samba/smbusers
security = user
guest ok = yes

Given it's location in smb.conf Samba will interprit it as a global parameter and apply it to all shares unless the individual share definition overrides it like the [Backup] share. So if you don't want guest access in say this share:

[sysvol]
path = /var/lib/samba/sysvol
read only = no

I would remove the "guest ok = yes" line after the "security = user" line in smb.conf.

[stimpe]

awesome, I fixed all of that, thanks!
One last question however is when I try to access my 'backup' share now (from windows 7 box) it asks me to authenticate, I enter the 'landon' user and password I just set and it tells me access denied. I think it might be because the domain is the computer name on windows 7...Do I need to setup a custom domain on my home network for this to work properly?

[altair4]

May I ask why you have this line in your smb.conf:

server role = domain controller

That's not something you have in a home network.

What experience I have is only with home LAN's not corporate networks so how a Domain Controller impacts all of this is above my pay grade.

[stimpe]

I dont know, I think it installed like that. What should it be set to? Either way I still cannot login to my samba shares through windows7 box(comp name: beast) if it keeps wanting me to authenticate through windows7domain (domain: beast). You'd want it to authenticate through samba, get what im saying? attached is a screenshot.

http://imageshack.us/photo/my-images/341/25902568.png/

[altair4]

Are you by any chance running with Samba4 ?

If you run the following command:

Code: Select all

dpkg -l samba

Does it come back with a "samba 2:3.something" or a 2.4.something.

Samba3 is the default - Samba4 is something that's not quite ready for prime time.

[stimpe]

Are you by any chance running with Samba4 ?

If you run the following command:

Code: Select all

dpkg -l samba

Does it come back with a "samba 2:3.something" or a 2.4.something.

Samba3 is the default - Samba4 is something that's not quite ready for prime time.

You've told me this in a previous thread, I removed samba4 a while ago, here is output from command

Code: Select all

server@server-mint ~ $ dpkg -l samba
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name              Version       Architecture  Description
+++-=================-=============-=============-=======================================
ii  samba             2:3.6.6-3ubun amd64         SMB/CIFS file, print, and login server 

[altair4]

Go back into smb.conf and put a # in front of the line so that it looks like this:

;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

#server role = domain controller
username map = /etc/samba/smbusers
security = user

Then restart samba again:

Code: Select all

sudo service smbd restart

I'll have to check my sources but I don't think there is an explicit "server role" parameter in smb.conf for Samba3. There is for Samba4. Maybe some mixing up between the 2 in smb.conf. Anyway you can always set it back again if it doesn't resolve the issue.

[stimpe]

no change, attached is screenshot of what it says after i try and use my samba username/pass. I thought it might be having trouble between the Mint username 'landon' and SMB username 'landon' so i removed the Mint username, and still get the same error. just to be clear, they are seperate accounts..right?

http://imageshack.us/photo/my-images/577/45057792.png/

[altair4]

There is only one user. There can be 2 different passwords for that user - one to login to the machine itself and one to use for samba.

I don't know what you mean when you say you removed the Mint user. Isn't that your login user name?

[altair4]

I just noticed this in your smb.conf:

[netlogon]
path = /var/lib/samba/sysvol/localdomain/scripts
read only = no

That's another Samba4 thing I think. Especially since there is no /var/lib/samba/sysvol directory in Mint / Ubuntu.

I'm trying to think of the best way to reset ourselves here.

[altair4]

Please post the output of the following command:

Code: Select all

testparm -s /usr/share/samba/smb.conf

[stimpe]

the users i have on mint:
server@server-mint (the main login)
and i created
landon@server-mint for the purpose of logging in through this account to access samba shares - but i think samba uses its own username/password list so i removed it (sorry if this is confusing)

testparm

Code: Select all

server@server-mint ~ $ testparm -s /usr/share/samba/smb.conf
Load smb config files from /usr/share/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
        server string = %h server (Samba, LinuxMint)
        encrypt passwords = No
        map to guest = Bad User
        obey pam restrictions = Yes
        pam password change = Yes
        passwd program = /usr/bin/passwd %u
        passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
        unix password sync = Yes
        syslog = 0
        log file = /var/log/samba/log.%m
        max log size = 1000
        dns proxy = No
        usershare allow guests = Yes
        panic action = /usr/share/samba/panic-action %d
        idmap config * : backend = tdb

[printers]
        comment = All Printers
        path = /var/spool/samba
        create mask = 0700
        printable = Yes
        print ok = Yes
        browseable = No

[print$]
        comment = Printer Drivers
        path = /var/lib/samba/printers

i commented these lines out and no change:

Code: Select all

[netlogon]
path = /var/lib/samba/sysvol/localdomain/scripts
read only = no

[altair4]

(1) Make a backup of your current smb.conf

Code: Select all

sudo mv /etc/samba/smb.conf /etc/samba/smb.conf.bak

(2) Copy the default:

Code: Select all

sudo cp -a /usr/share/samba/smb.conf /etc/samba/

(3) Go to /etc/samba/smb.conf and correct the mistake:

encrypt passwords = false

Could also be listed as "no"
and change it to:

encrypt passwords = yes

(4) Add your share to the end of smb.conf:

Code: Select all

[LandonBackup]
path = /home/landon/Backup
browseable = yes
guest ok = no
read only = no
writeable = yes

(5) Restart samba

Code: Select all

sudo service smbd restart

Didn't quite follow the thing about landon but if you removed the landon user from smbpasswd add him back:

Code: Select all

sudo smbpasswd -a landon

There is only one user. You can add or delete him from the samba password database but there is only one "landon" user. In order to use a "landon" user form the samba client a "landon" user must first be created in Linux and then added to the samba database with the smbpasswd command.

[stimpe]

I did all that. The new share from the new smb.conf shows up fine but it still asks for the same authentication (reference my first screenshot of the login prompt in windows7)
http://imageshack.us/photo/my-images/341/25902568.png/ <-- previous screenshot, same authentication menu (note: domain:beast), where beast is the name of the windows7 box

I do not think there is anything wrong with how samba is configured, but how windows is trying to authenticate

[altair4]

Access it from Mint. Actually access the Samba server share form the samba client on the same Mint box.

[stimpe]

Access it from Mint. Actually access the Samba server share form the samba client on the same Mint box.

in Dolphin > Network > Samba shares nothing is showing up

[altair4]

Dolphin? Oh dear lord, KDE?

I have Win7 in this zoo so I will try to reproduce this problem but what version do you have. I have Win7 Pro's so if yours is Win7 Home I don't know how valid this will be.

It won't be today though since I should have shut down about 3 hours ago.