I am new to Linux and tried to make a Samba share, to access files on an external hard drive (ext4), mounted on my Linux system, from a mac and a PC. I followed the steps on Ubuntu's website, and I can navigate in the share, but only in read-only. I would like all my shares to work with read-write permissions to the designated users.

Here is my smb.conf file:

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

create mask = 0644
directory mask = 0755

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

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

[MOVIES]
    comment = MOVIES
    path = /media/MOVIES
    read only = no
    browsable = yes
    valid users = admin, myusername
    write list = admin, myusername

[DATA]
    comment = DATA
    path = /media/DATA
    read only = no
    browsable = yes
    valid users = admin, myusername
    write list = admin, myusername

[PUBLIC]
    comment = PUBLIC
    path = /media/DATA/PUBLIC
    read only = no
    browsable = yes
    valid users = admin, myusername, public
    write list = admin, myusername, public

I have a Raspberry Pi that is acting as a file server in my home and it has Samba installed.

Currently, Samba controls access to different hard drives/directories storing various media/data.

The pi account is the owner and is able to do anything with these folders when logged in. I am the only one with access to the pi account/password.

So far everything is working great.

However, I want to give other members of my family the ability to read anything in these folders, but not write. Also I do not wish to share the Pi login/password. For these reasons, I cannot simply give them the Pi login/password for them to access the Samba shares.

What I would like to do is the either have another account where they can login to use the Samba shares with read-only permissions, or better yet, access Samba without needing to log in at all (but with only read-only permissions). At the same time, I wish to allow Pi to continue to do anything including write to these folders, so I cannot simply change the directory permissions to disable write for instance. In other words, I want Pi to be able to write/delete/modify, everyone else just read.

I have a few questions:

1. Is it possible to access a Samba share without logging in to Linux? Right now, when I use \\raspberrypi\share_name to access a share from Windows, I am asked to log in first before being granted access. I believe that at this point I am actually logging in to Linux ,not Samba (correct me if I am wrong since both Linux and Samba have a Pi account with the same password, so I am not totally sure on this).

2. If I enable guest access to the Samba share, will other users still have to login to Linux to get access to the share? In other words, is Linux login required even if guest access is allowed in Samba?

3. A different question: does Linux, in particular Raspbian Linux, allow guest logins? This may not be entirely relevant to the Samba sharing question, but I am just simply curious as to whether guest access is permitted on Raspbian through the standard login (not Samba).

4. Either way, is there a way to allow my family members on the local network to simply map to the Samba shares without logging in, but only have read-only access? How can this be done?

5. And if not, as a second choice I can create an account for the family members which would be either an actual guest account (if Raspbian allows this) or a normal user account with the same intent as a guest account (everyone will just use it to login to access Samba shares). But if so, how would I allow them read-only access to the shares?

Thanks!

Simple Problem:

After updating to ios 18 i my smb nas is read only via Files App. Other tools can access my nas and write data.

So i waited for 18.2. Nothing fixed!

Anybody any Information about that? I will ask apple, but mostly they do not care.

Hello,

I've been trying to get the native iOS "Files" app to connect to my Ubuntu Samba server, but it only connects as read-only (the "New Folder" and paste options are grayed out).

The strangest part: ES File Explorer on the same iPhone connects to the exact same server with the same credentials and has full read/write access. This proves my server, permissions, and user credentials are correct.

This problem seems to be 100% with the Apple "Files" app. Has anyone found a definitive workaround?

My Setup

• Server: Ubuntu 22.04 Desktop

• Samba: Standard install

• Network: Accessing from my iPhone via Tailscale (using the 100.x.x.x IP). (Also not working without tailscale and using local ip)

• User: my_user (PUID 1000).

Server-Side Checks (All Passed)

• Samba Config: All shares are writable = yes, valid users = my_user, and write list = my_user.

• Linux Permissions: All shared folders are owned by my_user:my_user with full rwx permissions for the owner.

• Samba Password: The smbpasswd for my_user is correctly set and synced.

• Firewall & Security: ufw is inactive. AppArmor and SELinux are not enabled or enforcing on smbd.

• Network: ss -ltnp confirms smbd is listening on all interfaces (0.0.0.0 and [::]), correctly capturing Tailscale traffic.

Failed Fixes for iOS Files App

• Rebooted server and restarted smbd service.

• Ejected and reconnected the server in the Files app.

• Tried removing force user from smb.conf to prevent conflicts.

• Tried disabling SMB signing (server signing = disabled).

• Full Apple VFS Fix: Applied the complete fruit and catia VFS object stack (vfs objects = catia fruit streams_xattr), added all fruit: directives (fruit:model = MacPro, etc.), and set ea support = yes on all shares. Got it from here: https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X

After all this, the native iOS Files app is still read-only, while ES File Explorer works perfectly. Any ideas?

I can't get my smb share to not be read-only, I just installed it on a raspberry pi and I've been messing with /etc/samba/smb.conf for a few hours and I get the sense this is supposed to be really easy. My share is:

[share]
Comment = Shared Folder
Path = /home/pi/mntThumbDrv
Browseable = yes
Writeable = yes
only guest = no
create mask = 0700
directory mask = 0700
;Public = yes
;Guest ok = yes
force user = pi

I just don't see why it's read-only on every device I've connected to it on

I upgraded from 11.3 to 12.0-U1 last weekend and mostly it was fine, except that now my SMB share is Read Only. I was before using root to access my server, which I realize has been disabled for security reasons, so I made a new user, new SMB share, and I've checked every single permission box I can see and I only have read access to the pool.

I do have write access to the new user's Home Directory, but that's kind of useless, all the media is in the rest of the pool.

For the SMB share I have it set to root of the pool as the path, and using Default share parameters. For it's Share ACL, I've given it SID S-1-1-0, Permission is FULL, Type=ALLOWED, Domain is blank, and Name=Everyone.

I'm at a bit of a loss how to get my new user to access the rest of my pool.

Hello

I have been struggling with a permission issue on one of my RHEL servers. Everytime I create a folder it is not writable by everyone. To me the smb.conf looks correct. Could someone show me what I am missing?

testparm -s

Load smb config files from /etc/samba/smb.conf

rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)

Processing section "[DNA]"

Processing section "[XSAN]"

Processing section "[XSANHD]"

Processing section "[LG]"

Loaded services file OK.

Server role: ROLE_STANDALONE

[global]

workgroup = home

map to guest = Bad User

preferred master = Yes

usershare allow guests = Yes

guest ok = Yes

[DNA]

path = /media/big-vol0/share1

read only = No

create mask = 0777

directory mask = 0777

force directory mode = 0777

veto files = /lost+found/

[XSAN]

path = /media/big-vol0/share2

read only = No

create mask = 0777

directory mask = 0777

veto files = /lost+found/

[XSANHD]

path = /media/big-vol0/share3

read only = No

create mask = 0777

directory mask = 0777

veto files = /lost+found/

[LG]

path = /media/big-vol0/share4

read only = No

create mask = 0777

directory mask = 0777

I can't write to my NAS from my iPhone using the same credentials that I use successfully for my Mac, Windows, and Linux. It is displayed as read-only

I'm currently copying the files from my Samba shares over to my computer so I can build a fresh image. Certain files, bios files for example, can't be copied. Tells me I don't have the proper permissions.

Is there any command I can run on the Pi to open up permissions to the entire device?