I have tried to share ntfs drives from Linux [SOLVED]

[dureal99d]

I have tried to share ntfs drives from Linux mint to linux/windows boxes without any success.

The drives show as available to my windows machines but are inaccessible (permission denied) when i click on them.

How do I set the appropriate permissions in Linux mint 14 mate so that linux/windows boxes can access shares on my linux mint box.

I have installed samba, winbind and configured them both.

Basicly what I am attempting to do is share my ntfs drives that are on my linux mint box with other machines on my network. I am having trouble performing this task due to permission problems when a windows/linux box attempts to access those shares.


I am able to access windows shares from mint with no issue. I can call up windows machines by host name and my mint box. my linux mint box machine responds by host name when called upon by a windows machine. I am just unable to access my ntfs shares on Linux mint from other machines on the lan.

help please & thank you

[altair4]

Note: I'm going to ignore the winbind comment and treat this like a home network.

There is not enough information to answer this question. Let's start with the output of the following commands:

Code: Select all

testparm -s

Code: Select all

net usershare info --long

And how are you mounting these NTFS partitions? In fstab? Or as needed through Caja?

[dureal99d]

Note: I'm going to ignore the winbind comment and treat this like a home network.

There is not enough information to answer this question. Let's start with the output of the following commands:

Code: Select all

testparm -s

Code: Select all

net usershare info --long

And how are you mounting these NTFS partitions? In fstab? Or as needed through Caja?

I am so new to Linux i don't know what to type to help you understand what i am trying to do. However i will try my best.

basically i am trying to share the root of my secondary ntfs drives similar to in windows where i can view remote content over the local LAN via windows or other Linux machines. which i have partially setup but i am unable to view content in folders as i somehow lack permission & nothing on my secondary drives as i apparently have no permission & dont know how to give myself permission.

as to how i mount my ntfs drives i do not understand this question. when i load the os (linux mint) i am simply able to access my drives.

[altair4]

I am making a lot of assumptions here because I don't have enough information to work with but .......

Open a terminal and type:

Code: Select all

gksu pluma /etc/samba/smb.conf

Find the workgroup = workgroup line and right under it enter the following:

Code: Select all

force user = altair

Change altair to whatever your Mint login user name is.
Then restart samba:

Code: Select all

sudo service smbd restart

If that doesn't fix it then I will need more information. Please post the output of the following commands:

Code: Select all

testparm -s

Code: Select all

cat /etc/fstab

[dureal99d]

direll@soulmint ~ $ testparm -s
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[printers]"
Processing section "[print$]"
Processing section "[direll]"
Processing section "[SoulDrive 2]"
Processing section "[Pull Drive 2]"
Processing section "[Pull Drive 1]"
Processing section "[SoulDrive]"
Processing section "[New Volume]"
Processing section "[Harddrive Templatesd2]"
Processing section "[bluray movies sd]"
Loaded services file OK.
WARNING: You have some share names that are longer than 12 characters.
These may not be accessible to some older clients.
(Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)
Server role: ROLE_STANDALONE
[global]
server string = %h server (Samba, LinuxMint)
map to guest = Bad User
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
unix password sync = Yes
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
dns proxy = No
usershare allow guests = Yes
panic action = /usr/share/samba/panic-action %d
idmap config * : backend = tdb
force user = direll

[printers]
comment = All Printers
path = /var/spool/samba
create mask = 0700
printable = Yes
print ok = Yes
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/printers

[direll]
path = /home/direll
guest ok = Yes

[SoulDrive 2]
path = /media/direll/SoulDrive 2
guest ok = Yes

[Pull Drive 2]
path = /media/direll/Pull Drive 2
guest ok = Yes

[Pull Drive 1]
path = /media/direll/Pull Drive 1
guest ok = Yes

[SoulDrive]
path = /media/direll/SoulDrive
guest ok = Yes

[New Volume]
path = /media/direll/New Volume
guest ok = Yes

[Harddrive Templatesd2]
path = /media/direll/SoulDrive 2/Harddrive Template
guest ok = Yes

[bluray movies sd]
path = /media/direll/SoulDrive/bluray movies
guest ok = Yes
direll@soulmint ~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' 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=dfaae108-eb49-4224-be26-6a047fa664f7 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=87fbd59b-418e-4396-83d3-ec49d030a353 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

[dureal99d]

#
# 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.master" and create the "real" config file with
# testparm -s smb.conf.master >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]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
force user = direll

# server string is the equivalent of the NT Description field
server string = %h server (Samba, LinuxMint)

# 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

# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = wins lmhosts hosts 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 = 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 #######

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

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

########## 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 director 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
# The following parameter makes sure that only "username" can connect
#
# 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

wins support = no
[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

# 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




[direll]
path = /home/direll
available = yes
browsable = yes
public = yes
writable = no

[SoulDrive 2]
path = /media/direll/SoulDrive 2
available = yes
browsable = yes
public = yes
writable = no


[Pull Drive 2]
path = /media/direll/Pull Drive 2
available = yes
browsable = yes
public = yes
writable = no

[Pull Drive 1]
path = /media/direll/Pull Drive 1
available = yes
browsable = yes
public = yes
writable = no

[SoulDrive]
path = /media/direll/SoulDrive
available = yes
browsable = yes
public = yes
writable = no

[New Volume]
path = /media/direll/New Volume
available = yes
browsable = yes
public = yes
writable = no

[Harddrive Templatesd2]
path = /media/direll/SoulDrive 2/Harddrive Template
available = yes
browsable = yes
public = yes
writable = no

[bluray movies sd]
path = /media/direll/SoulDrive/bluray movies
available = yes
browsable = yes
public = yes
writable = no

[altair4]

That looks perfect. So what's the problem?

You don't have these ntfs partition mounted at boot so you will have to mount them manually through the file manager first but other than that it looks like my assumption was correct. Only direll can gain access to the ntfs partitions and "force user= direll" will fix it.

[dureal99d]

That looks perfect. So what's the problem?

You don't have these ntfs partition mounted at boot so you will have to mount them manually through the file manager first but other than that it looks like my assumption was correct. Only direll can gain access to the ntfs partitions and "force user= direll" will fix it.

Ok! So how do I mount, or better yet how do I make them mount at boot up!! Also do I have to create a user for each windows user machine if I do not want to force direll

[altair4]

So how do I mount

Open up caja. On the left side panel should be something called "SoulDrive". Selecting that will mount the partition. Now that it's mounted you should be able to access it from the other machine.

or better yet how do I make them mount at boot up

This is going to get complicated. Having them defined in fstab is relatively easy but you are going to have to change the paths of most of your shares in smb.conf because of this bug and because you have spaces in the Labels of your partitions.

Anyway, please post the output of the following command:

Code: Select all

sudo blkid -c /dev/null -o list

[dureal99d]

direll@soulmint ~ $ sudo blkid -c /dev/null -o list
[sudo] password for direll:
device fs_type label mount point UUID
----------------------------------------------------------------------------

[altair4]

Open up caja. On the left side panel should be something called "SoulDrive". Selecting that will mount the partition. Now that it's mounted you should be able to access it from the other machine.

Did this work or not. If it didn't work then there's no point in going any further.

direll@soulmint ~ $ sudo blkid -c /dev/null -o list
[sudo] password for direll:
device fs_type label mount point UUID
----------------------------------------------------------------------------

Well, let's see here ..... there's 2 possibilies:

[1] You forgot to post the rest of the output.

[2] That is the only output.

If it's [2] then here too there is no point in going any further.

[dureal99d]

Yes once I mounted the partitions they worked well.

as relates to the output it is number 2.

you say there is no need to go any further? Is this a bad thing?

Am i to assume their is no way to auto-mount these drives in this distro of mint based on that comment.

[altair4]

Am i to assume their is no way to auto-mount these drives in this distro of mint based on that comment.

We need the uuid number for all these unmounted partitions. The blkid command is the way to get them. Let's try a shorter version:

Code: Select all

sudo blkid -c /dev/null

Or make it even smaller:

Code: Select all

sudo blkid

If even that doesn't work then see if this one has output:

Code: Select all

ls /dev/disk/by-uuid/ -alh

If the last one has output then you need to tell me which uuid belongs to which partition label. If you don't know then output the result of this command:

Code: Select all

ls /dev/disk/by-label/ -alh

[dureal99d]

direll@soulmint ~ $ ls /dev/disk/by-uuid/ -alh
total 0
drwxr-xr-x 2 root root 180 Jun 28 19:40 .
drwxr-xr-x 6 root root 120 Jun 28 15:47 ..
lrwxrwxrwx 1 root root 10 Jun 28 15:48 7290FEFE90FEC81D -> ../../sde1
lrwxrwxrwx 1 root root 10 Jun 28 15:48 87fbd59b-418e-4396-83d3-ec49d030a353 -> ../../sda5
lrwxrwxrwx 1 root root 10 Jun 28 15:48 A056771B5676F200 -> ../../sdd1
lrwxrwxrwx 1 root root 10 Jun 28 19:40 BA18373B1836F5CB -> ../../sdb1
lrwxrwxrwx 1 root root 10 Jun 28 15:48 DE6CD2BC6CD28EA1 -> ../../sdf1
lrwxrwxrwx 1 root root 10 Jun 28 15:48 dfaae108-eb49-4224-be26-6a047fa664f7 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jun 28 15:48 FAD0B04BD0B00FBD -> ../../sdc1
direll@soulmint ~ $ ls /dev/disk/by-label/ -alh
total 0
drwxr-xr-x 2 root root 140 Jun 28 19:40 .
drwxr-xr-x 6 root root 120 Jun 28 15:47 ..
lrwxrwxrwx 1 root root 10 Jun 28 15:48 New\x20Volume -> ../../sdf1
lrwxrwxrwx 1 root root 10 Jun 28 15:48 Pull\x20Drive\x201 -> ../../sdd1
lrwxrwxrwx 1 root root 10 Jun 28 15:48 Pull\x20Drive\x202 -> ../../sde1
lrwxrwxrwx 1 root root 10 Jun 28 15:48 SoulDrive -> ../../sdc1
lrwxrwxrwx 1 root root 10 Jun 28 19:40 SoulDrive\x202 -> ../../sdb1
direll@soulmint ~ $

[altair4]

There's a good chance I've mad a mistake somewhere in this comparison of the output but as far as I can tell this is how bklid should have listed your partitions if your install were fully functional:

/dev/sde1 7290FEFE90FEC81D "Pull Drive 2"
/dev/sdd1 A056771B5676F200 "Pull Drive 1"
/dev/sdb1 BA18373B1836F5CB "Soul Drive 2"
/dev/scd1 FAD0B04BD0B00FBD "SoulDrive"
/dev/sdf1 DE6CD2BC6CD28EA1 "New Volume"

That last one is admittedly a flat out guess since it doesn't appear to have a label at all.

[1] Create a permanent home for these partitions - I have purposely made these without spaces in their names:

Code: Select all

sudo mkdir /media/PullDrive2
sudo mkdir /media/PullDrive1
sudo mkdir /media/SoulDrive2
sudo mkdir /media/SoulDrive
sudo mkdir /media/NewVolume

[2] Just in case you have mounted any of these make sure they are unmounted:

Code: Select all

sudo umount "/media/direll/Pull Drive 2"
sudo umount "/media/direll/Pull Drive 1"
sudo umount "/media/direll/Soul Drive 2"
sudo umount "/media/direll/SoulDrive"
sudo umount "/media/direll/New Volume"

[3] Edit fstab as root:

Code: Select all

gksu pluma /etc/fstab

[4] Add the following lines to the end of fstab:

Code: Select all

UUID=7290FEFE90FEC81D /media/PullDrive2 ntfs defaults,nls=utf8,umask=000,uid=1000,windows_names 0 0
UUID=A056771B5676F200 /media/PullDrive1 ntfs defaults,nls=utf8,umask=000,uid=1000,windows_names 0 0
UUID=BA18373B1836F5CB /media/SoulDrive2 ntfs defaults,nls=utf8,umask=000,uid=1000,windows_names 0 0
UUID=FAD0B04BD0B00FBD /media/SoulDrive ntfs defaults,nls=utf8,umask=000,uid=1000,windows_names 0 0
UUID=DE6CD2BC6CD28EA1 /media/NewVolume ntfs defaults,nls=utf8,umask=000,uid=1000,windows_names 0 0

[5] Now run the following command which tests for syntax errors and if there are none silently mounts these partitions with the new mount instructions in fstab:

Code: Select all

sudo mount -a

[6] Verify that you can access these partitions locally.

[7] Go into whatever you are using to create the current samba shares and remove the old shares and replace them with new ones pointing to the new mount points.

[dureal99d]

First of all allow me to say thank you for all of your help. I have learned so much from you.

1. bklid did not work it just produced a blinking curser the only commands that did work were the 2 I posted which resulted in the 2 outputs you observed.

2 I shall try these configurations as soon as I get home & get back to you as to if they work which based on all of your prior instruction i fail to see a non working outcome.

3. i dont fully understand what you mean by Go into whatever you are using to create the current samba shares and remove the old shares and replace them with new ones pointing to the new mount points.

[altair4]

3. i dont fully understand what you mean by Go into whatever you are using to create the current samba shares and remove the old shares and replace them with new ones pointing to the new mount points.

For example, somehow you created this this entry in /etc/samba/smb.conf:

[Pull Drive 2]
path = /media/direll/Pull Drive 2
available = yes
browsable = yes
public = yes
writable = no

That share won't work any longer because that partition is now mounted to: /media/PullDrive2

I don't know what mechanism you used to create the original share ( a utility, Caja itself, direct edit of smb.conf with pluma ? ) but you need to change the path to point to the new mount point so that when you look at smb.conf it looks like this:

[Pull Drive 2]
path = /media/PullDrive2
available = yes
browsable = yes
public = yes
writable = no

If you do a direct edit remember that you need to restart samba services after editing and saving smb.conf:

Code: Select all

sudo service smbd restart

[dureal99d]

Ooooh ok, now i understand.

I shall implement these changes as soon as I get off duty.

One sideline question, i use linux mint which is debian based from what i understand, or i guess based in ubuntu build im not really sure which is true and which is not when referring to Debian vs Ubuntu builds or if their is any difference or similarity between the 2 at all.

So are these methods you are teaching me to use able to be used say in ubuntu or kde or what ever build i so choose to use in the near or late future to accomplish the same results as relates to auto mounting drives speaking on debian/ubuntu builds only?