Ubuntu Question 1: Share Folders

bchip

Senior Member
Joined
Mar 12, 2013
Messages
875
Hi Guys

Finally took the plunge and started working on Linux / Ubuntu for the first time ever.
I'm rooting for Linux but this is seriously frustrating...
It seems though that most of my frustrations come in when mixing Windows stuff with Linux stuff.
Hopefully I can post a couple of questions here.

I have a windows computer and a now my linux file server thats running.
I've gotten it right that the 2 can see one another. I've created a share folder on my Linux server called "Uploads"
so if I want to copy anything across (my understanding) is that I can copy/change/edit/etc any files in here from my other computers.

I've set the folder as
- Share Folder : Yes
- Allows others to access and edit this folder : yes
- Allow guest / anonymous access: yes

If I copy/paste a folder from my Win 10 to this folder it locks everything.
So then you have to go chmod 777 folder...only to find out that nothing below it has changed, only the folder itself
so then there's the recursive function chmod 777 -R folder and it only works for that specific folder (some of it, 1 file was ignored).

Then I read somewhere that you actually suppose to edit the samba config file...so I edit /etc/smb.conf
[make a backup first] and change it that
directory mask = 0700 changes to directory mask = 0775
create mask = 0700 changes to create mask = 0775

I restarted the samba process [sudo services smb & nmb restart] and low and behold smb.conf is now blank.
Luckily had the backup, placed it all back and I can connect again, and its with the 0775
but nothing else has changed...if I copy/paste a folder its still all locked.

Any help would be appreciated
 

Fyson

Well-Known Member
Joined
Jul 30, 2012
Messages
209
Hi, i'm new to linux too.
lost 4tb of data and decided to build ubuntu file server with new hard drives and an old socket 1150 mobo and cpu i had spare.

long story short, ubuntu works great. Apart from i can't access the drvies.
i've managed to initialize and partition them
they are set up as shared
My Windows 10 PC can see the Ubuntu pc under networking and can see the 3 drives. But can't access anything.
Its been 7 hours straight of me trying to get this to work. can anyone help me out?
Its fkn past 3 AM. i'm going to bed now.

I'm almost at the point of just installing windows 7 on it. i'll have other problems then but at least i know i will be able to access shared folders then.

I've enabled guest access on 2 of the 3 drives
can't access them at all - get the following error: you do not have permission to acess blablablablabalblabla
the other drive, where guest access is turned off i can type a username and password, but theres a "Access is denied." in red before i can even type anything.
 

Attachments

Last edited:

Fyson

Well-Known Member
Joined
Jul 30, 2012
Messages
209
#
# 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]

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

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = yes

# 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

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

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

# 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
 

Fyson

Well-Known Member
Joined
Jul 30, 2012
Messages
209
I'm going to reinstall ubuntu 18.04 since i think i might have messed up trying all the fixes for samba that i could find.

When i did a trial run on my old laptop, i installed 16.04 to test and when i shared a folder it imidiately asked me if i wanted to install samba to share to Windows. i did and i could access it on my windows pc without any hassle.

Not sure if 18.04 changed something or if i should rather stick to 16.04
 

Attachments

Fyson

Well-Known Member
Joined
Jul 30, 2012
Messages
209
reinstalled 16.04
created a shared folder (test)
installed samba
try to access that folder on windows
"windows cannot access" FFS
 

Attachments

Düber

Senior Member
Joined
May 17, 2018
Messages
601
I'm not an expert but I had problems with this too, I forget exactly how I came right(alot of googling) but basically I had different versions of Samba running on the computers.
The newest(most secure) version needs the whole path to the share entered before you can connect. The older versions would show all the share's on a machine. Windows 10 will only connect to the newest(think it's version 3) one.
You need a line in your smb.conf on the server to define which versions are allowed.
The main smb.conf can also be overruled by other config file (smb.local.conf or something like that) so check those too if they exist. One is in the /etc/samba/ folder the other is in your home folder, but only if they were created by you or a program.
Hope this helps.

Edit- attached a sample smb.conf from one of my SBC. (please don't criticise the loose permissions:))
 

Attachments

Last edited:

ArtyLoop

Executive Member
Joined
Dec 18, 2017
Messages
6,809
You also need to set the permissions on the folder you wish to share... so a good dose of chown command
 

Fyson

Well-Known Member
Joined
Jul 30, 2012
Messages
209
I can see why people love linux. but i fkn hate it right now.
Something that should be simple has turned into a 2 day nightmare.

I can't spend more time on this so i'm using windows 7 at the moment.
At least till I understand linux better and sort it out to do what i want it to.

For someone who just want to google, netflix, email i would definitely recommend ubuntu, (in fact i'm going to install it on my laptop) but once you need just a bit more it bites you in the ass.

The fact that i could set up a network share so easily the first time round (when testing) is incredibly infuriating.
Just installed samba, did something with nautilus (permissions i think, can't remember. it popped up right after samba installed) and done. Could access from all devices.
 
Last edited:

SilverNodashi

Expert Member
Joined
Oct 12, 2007
Messages
3,316
Keep in mind, with Linux, that a shared folder inherits the "root folerder's" permissions.

i.e. if you created a folder, say /home/bchip/Uploads, you need to access it as the user bchip, unless you specifically gave it other permissions.

Now, if you shared a folder, say /var/www/html/uploads, it would inherent root permissions, since root owns /var/

If that makes sense?

Please past your working smb.conf file, as well as the permissions of the folder(S) you want to share?

And, make sure the user you want to use is in the smbpassword file by running "smbpasswd -a bchip"
 

SilverNodashi

Expert Member
Joined
Oct 12, 2007
Messages
3,316
I can see why people love linux. but i fkn hate it right now.
Something that should be simple has turned into a 2 day nightmare.

I can't spend more time on this so i'm using windows 7 at the moment.
At least till I understand linux better and sort it out to do what i want it to.

For someone who just want to google, netflix, email i would definitely recommend ubuntu, (in fact i'm going to install it on my laptop) but once you need just a bit more it bites you in the ass.

The fact that i could set up a network share so easily the first time round (when testing) is incredibly infuriating.
Just installed samba, did something with nautilus (permissions i think, can't remember. it popped up right after samba installed) and done. Could access from all devices.
If you're very new to Linux, it might help to use something like Webmin to setup the shares.
 
Top