bks@bally-server:~$ ls -a /home/bks/NAS . .. Main_Drive Wallpapers
Hmm… maybe they have to be hard links …
BUT
after looking through your smb.conf … it looks like you may already have a directory specifically for sharing stuff
what’s the output from
ls -a /home
and
ls -a /home/share
?
bks@bally-server:~$ ls -a /home . .. bks share
bks@bally-server:~$ ls -a /home/share . .. it-works.txt
And on your laptop, when you enter
smb://192.168.0.8/share
in the pcmanfm address bar.
can you see that
it-works.txt
file … and can you edit it ?
Yes I can access that folder and edit that file.
OK, let’s go about this a different way then, and mount the drive/partitions directly into (a directory we’ll create) there then 
First create the mount points
sudo mkdir /home/share/NAS
sudo mkdir /home/share/NAS/Wallpapers
sudo mkdir /home/share/NAS/Share
now open fstab for editing:
sudo nano /etc/fstab
and change the 2 bottom lines so it reads:-
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=ff0a5255-09f5-4b23-a2d2-8db9cebc726d / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=652469de-ef92-47ea-8e42-25deb43687fe none swap sw 0 0
/dev/sdb1 /home/share/NAS/Share ext3 rw,errors=remount-ro 0 0
/dev/sdc1 /home/share/NAS/Wallpapers ext3 rw,errors=remount-ro 0 0
SAVE fstab.
open /etc/samba/smb.conf for editing
sudo nano /etc/samba/smb.conf
and remove that new section you added at the bottom …
Then find the section that reads
[share] path = /home/share writeable = yes guest ok = yes guest only = yes create mode = 0777 directory mode = 0777 share mode = 0777
and change it to
[NAS] path = /home/share/NAS writeable = yes guest ok = yes guest only = yes create mode = 0777 directory mode = 0777 share mode = 0777
SAVE the smb.conf file.
Reboot the server.
On the laptop, try:
smb://192.168.0.8/share/NAS
Can you see the shares called “Wallpapers” and “Share” ?
Can you create and edit stuff on them ?
If so, we’ll clean up the old now unused mount points and ~/NAS-Shares directory.
Is it neccesary to complicate things?
He already has this entry in fstab:
/dev/sdb1 /mnt/NAS-200GB ext3 rw,errors=remount-ro 0 0 /dev/sdc1 /mnt/NAS-20GB ext3 rw,errors=remount-ro 0 0
To start with create a /shared directory on each drive
sudo mkdir /mnt/NAS-20GB/shared
sudo mkdir /mnt/NAS-200GB/shared
Next change the permissions (allow access to everyone) on each newly created folder:
sudo chmod 0777 /mnt/NAS-20GB/shared
sudo chmod 0777 /mnt/NAS-200GB/shared
Then edit the samba config file:
nano /etc/samba/smb.conf
Remove previously added shares, then add 2 new entries (one per shared drive):
[Share]
comment = Public Folder
path = /mnt/NAS-200GB/shared
available = yes
browseable = yes
public = yes
writable = yes
create mask = 0777
directory mask = 0777
[Wallpapers]
comment = Wallpapers Folder
path = /mnt/NAS-20GB/shared
available = yes
browseable = yes
public = yes
writable = yes
create mask = 0777
directory mask = 0777
directory mask = 0777
SAVE the smb.conf file.
Reboot the server.
Now try on laptop:
smb://192.168.0.8/
You should see folders
Share & Wallpapers
Sorry Mark, not trying to step on your toes.
You could do it that way … but if your edits to smb.conf are ADDED (leaving the original [share] section), that leaves /home/share accessible and writeable from other machines … effectively meaning people can save stuff on his system drive.
I thought it was “neater”, creating a NAS directory in /home/share … then EDITING the [share] section in smb.conf
the new mount points were just tidying up in case of problems … but yeh, I suppose they were unnecessary
You could do it that way .. but if your edits to smb.conf are ADDED (leaving the original [share] section),
That is why I am asking to remove the previous shares from the smb.conf file 
I am for simple life. By adding the shared directories on each drive will allow him to put
stuff there (outside of shared) what he does not necessarily want to share out.
Ahh … OK, I was just trying to be neat… having a single smb.conf entry … and keep it all in one place, but your way is just as valid, and I suppose slightly less work at the server end … but if he decides to mount the shares on the clients, my way will only need a single entry in the clients fstab
Also, I gather he wants to add another drive later … so it would only need a mountpoint and an fstab entry … done
I do agree I was over complicating things originally though … with the symlinks
Besides which, my missus says I’m good at over complicating things … so why change what I’m “good at”
She also says I like to be “right” all the time … so I’ll shut up now, just to prove her wrong … erm, now I’m confused :o
You are not alone. I get that from my missus too.
As a minor point, should BkS follow your instructions then what would stop other users creating folders in the NAS (writable) folder:
[NAS] path = /home/share/NAS writeable = yes guest ok = yes guest only = yes create mode = 0777 directory mode = 0777 share mode = 0777
Hmm … good point.
See, I’m not always right … so she must be wrong … does that make me right again … doh! ???
I can see “Share” & “Wallpapers” in smb://192.168.0.8/share
However I get denied permission to create any files. In either directory.
Let’s start again and do it SeZo’s way … as he pointed out there is a glaring hole (that allows users to write to your main system hard drive) in my solution :-[
what are the contents of:
nano /etc/fstab
and the output from:
ls -a /mnt
and
ls -a /home/share
and the contents of:
nano /etc/samba/smb.conf
and we’ll get it right this time
His way will also allow you to put stuff on those drives that ISN’T shared if you ever wanted to.
sighs… ok.
# /etc/fstab: static file system information. # # Use 'blkid -o value -s UUID' to print the universally unique identifier # for a device; this may be used with UUID= as a more robust way to name # devices that works even if disks are added and removed. See fstab(5). # # proc /proc proc nodev,noexec,nosuid 0 0 # / was on /dev/sda1 during installation UUID=ff0a5255-09f5-4b23-a2d2-8db9cebc726d / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=652469de-ef92-47ea-8e42-25deb43687fe none swap sw 0 0 /dev/sdb1 /mnt/share/NAS/Main_Drive ext3 rw,errors=remount-ro 0 0 /dev/sdc1 /mnt/Wallpapers ext3 rw,errors=remount-ro 0 0
bks@bally-server:~$ ls -a /mnt . .. NAS-200GB NAS-20GB
bks@bally-server:~$ ls -a /home/share . .. it-works.txt NAS
smb.conf contents:
[spoiler]#
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.maste r” and create the “real” config file with
testparm -s smb.conf.maste r >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]
unix charset = UTF-8
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 = 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 = 192.168.0.8/24 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 = share
You may wish to use password encryption. See the section on
‘encrypt passwords’ in the smb.conf(5) manpage before enabling.
encrypt passwords = true
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
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 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
; share modes = no
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
[share]
path = /home/share/NAS
writeable = yes
guest ok = yes
guest only = yes
create mode = 0777
directory mode = 0777
share mode = 0777
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[/spoiler]
Firstly … I know why you couldn’t write to those shares … the last 2 lines in your fstab were totally wrong … those directories don’t exist, so the partitions wouldn’t have been getting mounted at all :o
OK … editing fstab …
sudo nano /etc/fstab
edit the last 2 lines, so it reads:-
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=ff0a5255-09f5-4b23-a2d2-8db9cebc726d / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=652469de-ef92-47ea-8e42-25deb43687fe none swap sw 0 0
/dev/sdb1 /mnt/NAS-200GB ext3 rw,errors=remount-ro 0 0
/dev/sdc1 /mnt/NAS-20GB ext3 rw,errors=remount-ro 0 0
SAVE fstab
reload fstab
sudo mount -a
create the 2 “share” directories … and make them writeable by everyone:
sudo mkdir /mnt/NAS-20GB/share
sudo mkdir /mnt/NAS-200GB/share
sudo chmod 777 /mnt/NAS-20GB/share
sudo chmod 777 /mnt/NAS-200GB/share
Editing smb.conf -
REMOVE (or comment out) the section I’ve highlighted in RED
and add the 2 new sections I’ve highlighted in GREEN at the bottom.
sudo nano /etc/samba/smb.conf
[spoiler]
#[/spoiler]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.maste r” and create the “real” config file with
testparm -s smb.conf.maste r >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]
unix charset = UTF-8Browsing/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 = 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 = 192.168.0.8/24 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 = share
You may wish to use password encryption. See the section on
‘encrypt passwords’ in the smb.conf(5) manpage before enabling.
encrypt passwords = true
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
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/printcapCUPS 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/bashThe 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 = yesSetup 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 = noBy 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
; share modes = noUn-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[share]
path = /home/share/NAS
writeable = yes
guest ok = yes
guest only = yes
create mode = 0777
directory mode = 0777
share mode = 0777Windows 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 = noUncomment 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 = yesThe 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[b]# NAS-20GB added by BkS
[Wallpapers]
comment = Wallpapers Folder
path = /mnt/NAS-20GB/shared
available = yes
browseable = yes
public = yes
writable = yes
create mask = 0777
directory mask = 0777NAS-200GB added by BkS
[Share]
comment = Public Folder
path = /mnt/NAS-200GB/shared
available = yes
browseable = yes
public = yes
writable = yes
create mask = 0777
directory mask = 0777[/b]
SAVE the file.
REBOOT the server.
On the laptop …
When the server has rebooted … (on the laptop) log off, and on again.
Now try:-
smb://192.168.0.8/
What can you see ?
If as expected you can see the Share and Wallpapers directories, can you write to them ?
Only do this once everything is working (or you can just leave them … up to you) …
cleaning up the old attempts -
sudo rm -r /home/bks/NAS-Shares
sudo rm -r /home/share/NAS
If you’d rather use UUID’s than /dev/sdXY in fstab … let me know, and send the output from:
blkid
You can still do all the above first … then change to UUID’s later, once it’s all working.
Before you shout at me for changing the mount points back … I KNOW it wasn’t 100% necessary … I’m just putting them back in /mnt where they belong
Before you shout at me for changing the mount points back .. I KNOW it wasn't 100% necessary .. I'm just putting them back in /mnt where they belong ;)
I would not dream of shouting at you. 
On the other hand, it might be worth (to start with) to un-comment the ’ security = share’ in smb.conf
to allow access by others on the Lan without the need for user/password
####### 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 = share
security = share
Also there is a mismatch in the directories:
sudo mkdir /mnt/NAS-20GB/share
sudo mkdir /mnt/NAS-200GB/share
and
/mnt/NAS-20GB/shared
/mnt/NAS-200GB/shared
in the smb.conf
I can see the directories, although I cannot enter them. I get the same errors as before. and yes I fixed his error.