Guest access to samba shares

I need to share a directory to a few Windows machines, but they must be able to access the shares without the use of credentials (basically I need to give guest access to a samba share).

Unfortunately I can’t seem to find a solution, even after reading hundreds of tutorials… and Windows keeps saying that it’s impossible to access the share (it does not even ask for a password, just says it has “insufficient authorizations”).
Samba really is a bi*ch!! :rofl:

Anyway, here is my smb.conf:


   workgroup = WORKGROUP
   server string = %h server
   dns proxy = no
   log file = /var/log/samba/log.%m
   max log size = 1000
   syslog only = no
   syslog = 0

   panic action = /usr/share/samba/panic-action %d

   security = user
   guest account = nobody
   encrypt passwords = true
   passdb backend = tdbsam
   obey pam restrictions = yes
   unix password sync = yes

   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
   pam password change = yes
   map to guest = bad user

   load printers = no

   comment = DietPi Share
path = /mnt/dietpi_userdata
   browseable = yes
   create mask = 0775
   directory mask = 0775
   valid users = root
   writeable = yes

   comment = DietPi MiniNAS Share
path = /root/MiniNAS
   browseable = yes
   read only = no
   guest ok = yes

I have chowned and chmodded the MiniNAS directory in order for it not to be a “possession” of user ‘root’ anymore:

root@DietRasPi:~# l
total 44
-rw------- 1 root   root    9392 Jan  7 16:52 .bash_history
-rw-r--r-- 1 root   root     645 Nov  6 18:58 .bashrc
drwxr-xr-x 4 root   root    4096 Dec 29 18:09 .config
drwxr-xr-x 2 root   root    4096 Nov  7 18:35 Desktop
drwxrwxrwx 5 nobody nogroup 4096 Jan  7 16:39 MiniNAS
-rw-r--r-- 1 root   root     140 Nov 19  2007 .profile
-rw-r--r-- 1 root   root      66 Dec  7 15:46 .selected_editor

But I still can’t access it.
dietpi_userdata can be regularly accessed by providing root’s credentials.
Any suggestions?

EDIT: the only working solution I have found is to add

force user = root

to the MiniNAS folder definitions, but I think this is a very unsecure solution, and that a proper (different) way should be found.

well if you install webmin it’s really easy to configure permissions …

well, it shouldn’t be necessary to install anything in order to create a simple guest accessable samba share, imho. :wink:

agreed, i still prefer using a gui to manage things, but when it comes to it, i am sure it’ll be easy to manage to (on cli)

anyhow, see if this helps , my smb.conf

root@DietPi:/usr/share/samba# cat 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


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



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

workgroup = WORKGROUP

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


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



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


; 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 =======================

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.

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.)

; 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

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

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

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


Thanks, but I don’t see any guest accessable shared folders in your configuration file… :thinking: :wink:

but i am using it … i don’t need to put any credentials to login and see the files :confused:
i know this because i watched a movie on my smartphone through it and it didn’t ask for a thing …

In what folder was this movie stored?
I can’t see any shared folders in your smb.conf except from the home directories which are set as not browseable! :open_mouth:

look at the gui then

Those are the settings for the share called “dietpi”.
In the configuration file you posted that share is not present, so I guess you posted the wrong file :slight_smile:
Maybe webmin uses a separate file?

i don’t really know, maybe yes, but i don’t know why, right now, i entered on vlc the share, and it didn’t workd with “nobody”, “anonymous”, or “guest” users, so i am clueless :-/

and i had to use the user root with the corresponding password, of course, and it did work everything normal

but you say it maybe uses different conf files, that maybe a hit , let me search , so i can compare and if i find something , i’ll let you know

Yes, of course. If you provide root credentials it will work.
I’m using a work around by forcing user root and by limiting the access only to selected IP addresses.
It’s not the right way to do it, but it has to do until I find a better solution to this problem.

Post the results of:

cat /etc/samba/smb.conf