I recommend to create a dedicated user for that share and specify it in force user(see docs).

Create a user (shareuser for example) and set the owner of everything in the share folder to that user:

adduser --system shareuser
chown -R shareuser /path/to/share

Then add force user and permission mask settings in smb.conf:

[myshare]
path = /path/to/share
writeable = yes
browseable = yes
public = yes
create mask = 0644
directory mask = 0755
force user = shareuser

Note that guest ok is a synonym for public.

Answer from yaegashi on Stack Exchange
Top answer
1 of 5
103

I recommend to create a dedicated user for that share and specify it in force user(see docs).

Create a user (shareuser for example) and set the owner of everything in the share folder to that user:

adduser --system shareuser
chown -R shareuser /path/to/share

Then add force user and permission mask settings in smb.conf:

[myshare]
path = /path/to/share
writeable = yes
browseable = yes
public = yes
create mask = 0644
directory mask = 0755
force user = shareuser

Note that guest ok is a synonym for public.

2 of 5
6

In the share settings in smb.conf, you'll need to specify the names of users and/or groups that are allowed to write to the share, using a write list = ... line.

Example:

[myshare]
...
write list = my_linux_username

Then you'll need to use the smbpasswd command to set up a password to authenticate my_linux_username for Samba:

sudo smbpasswd -a my_linux_username

This step is necessary because the standard system passwords in /etc/shadow are hashed in algorithms that are incompatible with the password hash algorithms used in the SMB protocol. When a client sends a SMB authentication packet, it includes a hashed password. It can only be compared to another password hash that uses the same algorithm.

(Very, very old instructions from the previous millennium may recommend disabling password encryption in Samba, and using certain registry hacks to allow Windows to emit unencrypted passwords to the network. This advice is obsolete: those registry hacks may no longer work in current versions of Windows, and allow anyone who can monitor your network traffic to trivially capture your password.)


There's one more thing you may have to do client-side. When your Windows client system is joined to an Active Directory domain and you're logged in with an AD account, it automatically prefixes all unqualified usernames with the name of the AD domain of the user, i.e. you will be authenticating as AD_DOMAIN\your_username, not just your_username.

If you are logged in with a local account (or your client system is not joined to an AD domain), Windows may automatically prefix the username with the client hostname unless you specify another domain name.

To successfully log in to a stand-alone Samba server from a stand-alone Windows client, you may have to specify your username as SAMBA_SERVER_HOSTNAME\your_username.

Otherwise Samba will see the username as WINDOWS_CLIENT_HOSTNAME\your_username, conclude that it has no way to verify any users belonging to domain named WINDOWS_CLIENT_HOSTNAME, and will reject the login.

(Newer versions of Samba may have a built-in check for this specific situation, and they might allow you access nevertheless. But this is basically how SMB authentication works "under the hood", and if you need to deal with old versions of Samba, it might be useful still.)

🌐
Raspberry Pi Forums
forums.raspberrypi.com › board index › community › general discussion
How to make samba share writable? - Raspberry Pi Forums
Look at the uid/gid and mode options in your /etc/fstab and if there's nothing defined there look at what happens when you mount the USB stick with a mount command. Samba normally runs as root so you need to have uid=0,gid=0 and the right mode for the USB drive so that your smbd and nmbd tasks can share the drive out to the rest of your network.
🌐
Linux-training
linux-training.be › networking › ch18.html
Chapter 18. a writable file server
Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions [global] netbios name = TEACHER0 server string = Public Anonymous File Server security = SHARE [pubwrite] comment = files to write path = /srv/samba/writable read only = No guest ok = Yes [pubread] comment = files to read path = /srv/samba/readonly guest ok = Yes
🌐
nixCraft
cyberciti.biz › nixcraft › howto › linux › unix samba: make a share writable
UNIX Samba: Make A Share Writable - nixCraft
April 13, 2010 - and please if you use writeable = yes, write it correctly….. samba will accept both.
Find elsewhere
🌐
Linuxtopia
linuxtopia.org › online_books › network_administration_guides › using_samba_book › ch04_05_06.html
Using Samba - 4.5.1.5 read only and writeable
The options read only and writeable (or write ok ) are really two ways of saying the same thing, but approached from opposite ends. For example, you can set either of the following options in the [global] section or in an individual share: · If either option is set as shown, data can be read ...
Top answer
1 of 2
2

Remove samba by executing following commands

sudo apt-get remove --purge samba
sudo apt-get remove --purge smbclient libsmbclient
sudo apt-get purge samba samba-common
sudo rm -rf /etc/samba/ /etc/default/samba

Install it again

sudo apt-get install samba
sudo apt-get install smbclient libsmbclient

Now original smb.conf has been restored so restart Ubuntu then add user from terminal.

root@Dell-Inspiron-3521:~# sudo smbpasswd -a username (username should be without space eg "sudo smbpasswd -a alamjitsingh")
New SMB password:*********
Retype new SMB password:*********
Added user alamjitsingh.

Now edit smb.conf file as follows. Mentioned lines must be present in the the code.

sudo gedit /usr/share/samba/smb.conf


[global]
 workgroup = WORKGROUP
 passdb backend = tdbsam 
 security = user

[Optional] If you want to share folder which are inside opt directory then you also have to add following line in global section.

usershare owner only = False

In authentication section turn "map to guest = bad user" off by adding # at starting of code

#map to guest = bad user

At last add your personal code

   [sqr_custom]
path = /opt/oracle/psft/pt/ps_home8.55.11/sqr_custom
comment = Personal_Share
read only = no
available = yes
browseable = yes
writable = yes
guest ok = no
public = yes
printable = no
locking = no
strict locking = no

Apart from this your shared folder is in opt folder which require permissions to write. So firstly test this prog by sharing folder of home directory. Then we will proceed further. To know correct path of shared folder drag and drop folder on running terminal.


If you are succeed to run above code then do the following

To create a group:

sudo groupadd demoGroup

To add the user account to the group:

sudo usermod -G demoGroup username(eg alamjitsingh)

For setting permissions of writing

sudo chown -R username:groupname /opt/demo

eg

sudo chown -R alamjitsingh:demogroup /opt/demo

Following lines are for granting the write access to members of the demoGroup in directory demo (It will grant all demoGroup members to write)

sudo chgrp -R demogroup /opt/demo
sudo chmod 2770 /opt/demo

Restart services

sudo service nmbd restart
sudo service smbd restart

eg of shared folder of restricted directory with write privilege

[demo]
path = /opt/demo
comment = HD Share
read only = no
available = yes
browseable = yes
writable = yes
guest ok = no
public = yes
printable = no
locking = no
strict locking = no
force create mode = 0660
force directory mode = 2770
force user = alamjitsingh
force group = demogroup
2 of 2
1

Try below mentioned code

[global]
workgroup = WORKGROUP
netbios name = CDA
passdb backend = tdbsam 
security = user
#map to guest = Bad User
username map = /etc/samba/smbusers
guest account = nobody
guest ok = yes
log file = /var/log/samba.log.%m
log level = 2
max log size = 1000
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printing = bsd



[custom_home]
  path = /opt/asdf/custom_home
  read only = no
  available = yes
  browseable = yes
  writable = yes
  guest ok = no
  public = yes
  locking = no
  strict locking = no
  create mask = 0777
  directory mask = 0777
  valid users = @writer (if writer is not username remove this line i think, you added user name = testuser so remove this line)

Most probably testuser is your user name to access this shared folder. In windows 10 you have to "Add a Network Location" manually, eg- "\\192.168.1.3\ Shared_folder_name" then it will ask for username and password. Find this option->Add a Network Location in windows 10. In android devices you can access this shared directory via "ES file explorer" app. If still not working intimate me. Good luck.

🌐
LinuxQuestions.org
linuxquestions.org › questions › linux-server-73 › what's-the-difference-between-read-only=no-and-writable=yes-in-samba-756930
What's the difference between read only=no and writable=yes in Samba?
September 22, 2009 - What's the difference between read only=no and writable=yes in Samba? I see some docs stating read only=no means writable, then at this point, what's
🌐
Samba
samba.org › samba › docs › using_samba › ch09.html
Samba
When a user requests a connection to a share, Samba authenticates by validating the given username and password with the authorized users in the configuration file and the passwords in the password database of the Samba server. As mentioned earlier in the chapter, one way to isolate which users are allowed access to a specific share is by using the valid users option for each share: [global] security = user [accounting1] writable = yes valid users = bob, joe, sandy
🌐
Reddit
reddit.com › r/selfhosted › smb share only works in read-only
r/selfhosted on Reddit: SMB share only works in read-only
February 17, 2024 -

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

🌐
Reddit
reddit.com › r/proxmox › add/create write permission to samba share
r/Proxmox on Reddit: Add/create write permission to Samba share
March 2, 2024 -

I am so close to having this set up, I just need a little help with the last steps. I set up a samba share on my Proxmox server using this tutorial:

https://computingforgeeks.com/how-to-configure-samba-share-on-debian/

From my Windows PC I can see the Proxmox server on the network, I can login and see the demo files I created in the tutorial, but I can’t make any changes. Just keeps saying I don’t have permission. I have Plex in an LXC. From Windows I need to be able to navigate to the hdd and add media files over the local network. I thought I enabled write permission, but maybe I missed something.

Can someone please help me figure this out?

🌐
Samba
lists.samba.org › archive › samba › 2010-October › 159149.html
[Samba] writable = yes for Profiles in smb.conf.default
October 30, 2010 - Next message: [Samba] Samba 3.4.9 net rpc shutdown and XP Domain client · Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] On Sat, Oct 30, 2010 at 11:14 AM, Benedikt Panzer <Benedikt_Panzer at gmx.de> wrote: > I'm suggesting to add line 'writable = yes' for Profiles share in file examples/smb.conf.default.