Raspberry Pi_Eng_18.4.1 Remote Drive Connection Using SambProgram


Published Book on Amazon


All of IOT Starting with the Latest Raspberry Pi from Beginner to Advanced – Volume 1
All of IOT Starting with the Latest Raspberry Pi from Beginner to Advanced – Volume 2


출판된 한글판 도서


최신 라즈베리파이(Raspberry Pi)로 시작하는 사물인터넷(IOT)의 모든 것 – 초보에서 고급까지 (상)
최신 라즈베리파이(Raspberry Pi)로 시작하는 사물인터넷(IOT)의 모든 것 – 초보에서 고급까지 (하)


Original Book Contents


18.4   Remote Drive Connection

 

18.4.1  Remote Drive Connection Using <Samba> Program

 

18.4.1.1    Installing <Samba> Server Program

 

The <Samba> program allows you to use files of remote Raspberry Pi system as a network drive.

 

First, we install the <Samba> program as shown below.

 

pi@raspberrypi ~ $ sudo apt-get install samba

 

~ Skip

~ Skip

~ Skip

 

 

Then we install the <samba-common-bin> program as shown below.

 

pi@raspberrypi ~ $ sudo apt-get install samba-common-bin

 

~ Skip

~ Skip

~ Skip

 

 

To share the <Samba> server on the network, we need to add an account to <Samba>. We specify the account to use when connecting to the Raspberry Pi system from an external system such as MS Windows. The command prompts you for a password, which is the password you will use to connect to the network drive.

 

pi@raspberrypi ~ $ sudo smbpasswd -a pi

New SMB password:

Retype new SMB password:

Added user pi.

 

You then need to adjust the settings for the <Samba> server. To do this, edit the "/etc/samba/smb.conf" file and modify it as follows:

 

#

# 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

 

# server string is the equivalent of the NT Description field

   server string = %h server

 

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

 

[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.

# The following parameter makes 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

 

# 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

 

[root]

comment = raspberry pi samba server

path = /

valid user = pi

writable = yes

browseable = yes

 

[RootFolder]

comment = raspberry pi samba server

path = /

valid user = pi

writable = yes

browseable = yes

create mask = 0777

public = yes

 

Let's take a look at the configuration items one by one:

    [RootFolder]

This specifies a folder name used to connect.

We specify "\\raspberrypi\RootFolder" here.

 

    comment = raspberry pi samba server

This specifies a simple description.

 

    path = /                                      

This specifies a connected location on the folder of Raspberry Pi system.

We specify "root" directory here.

 

    valid user = pi                               

This specifies a user account used to connect.

We specify "pi" user here.

 

    writable = yes                               

This specifies whether Raspberry pie files can be edited/created/deleted.

If "no", it is read-only.

 

    browseable = yes

This is to specify whether to display the shared folder on the screen. Since it is not a setting for accessibility, it is possible to open the shared folder if only the permission is allowed.

 

    create mask = 0777             

This specifies the default value for the user permission to use when creating the file or directory.

 

    public = yes

This setting specifies whether shared folders are available to other users.

 

Once you have configured the <Samba> server, restart <Samba> server. You can restart the server with the following method.

 

pi@raspberrypi ~ $ sudo service samba restart

[ ok ] Stopping Samba daemons: nmbd smbd.

[ ok ] Starting Samba daemons: nmbd smbd.

 

You can also get the same effect if you start with the following method.

 

pi@raspberrypi ~ $ sudo /etc/init.d/samba restart

[ ok ] Stopping Samba daemons: nmbd smbd.

[ ok ] Starting Samba daemons: nmbd smbd.

 


 

18.4.1.2    Connecting from <Samba> Client

 

Once you have completed all the configuration work for <Samba> server in the Raspberry Pi system, you can connect from the client computer.

 

   Connecting from MS Windows computer

 

If your MS Windows computer is on the same LAN network as the Raspberry Pi system, you can easily access the file server in the Raspberry Pi system without any extra work.

 

If the MS Windows computer and the Raspberry Pi system are in the same LAN network, the Raspberry Pi computer is automatically included and displayed in the network search of the MS Windows computer. When you search [Network] in the [Explorer] of your MS Windows computer, you can see the Raspberry Pi system, and if you click Raspberry Pi system again, you can see the data of the folder specified in <Samba> server inside.


Figure 18‑5 Displaying network driver in MS windows

 

 

If the MS Windows computer is not on the same LAN network as the Raspberry Pi system, the Raspberry Pi system is not automatically visible. In this case, you must create an accessible network drive by specifying connection information for remote <Samba> server data separately. In order to create these network drives, you can use the ways of [Map network drive] or [Add a network location].

 

    [Map network drive] method

 

First, I will explain how to use [Map network drive] method. To use this method, click right mouse button on the [Computer] or [Network] icon in the right navigation pane of the [Explorer] window. Then, a pop-up menu will appear where you can run the [Map network drive] menu. When you run the menu, you will be prompted to specify the connection information for the network drive as follows. Here, specify the connection information to the <Samba> server of Raspberry Pi in the following format:

    Format       -- \\<Raspberry Pi Server>\<Samba server Name>        

    Example      -- \\raseberrypi\RootFolder      


Figure 18‑6 Mapping network driver in MS Windows

 

If you complete the setting and click the [Finish] button, it starts to connect to the file server. The first time you connect to the file server, the logon window will appear. You will use the "pi" account you used to set up <Samba> server and your password you specified when adding "pi" account.

 

When all connections are completed, a new network drive is created and displayed in [Computer] as shown below.


 

 

    [Add a network location] method

 

The next method to create a network drive is to use [Add Network Location] method. To use this method, click right mouse button on the [Computer] icon in the right-hand navigation pane of the MS Windows [explorer]. A pop-up menu will appear where you can run the [Add Network Location] menu.

 

When the menu is executed, the [add a network location] wizard] screen will appear as shown below. Choose [Choose a custom network location] and proceed. Then you will see a screen to specify the location for your network as follows, where you specify connection information about the <Samba> server of Raspberry Pi in the following format:

    Format       -- \\<Raspberry Pi Server>\<Samba server Name>

    Example      -- \\raseberrypi\RootFolder


Figure 18‑7 Adding a network location in MS Windows

 

 

If you complete the setting and click the [Next] button, it start to connect to the file server. The first time you connect to the file server, you will see the logon window, where you will use the "pi" account you used to set up <Samba> server and your password you specified when adding "pi" account.

 

When all connections are completed, a new network drive is created and displayed in [Computer] as shown below.


 

 

   Connecting from Apple Mac

 

To access from Apple Mac, Use the menu [Move] à [Connect to Server] from the [Finder] menu. Then, a screen to enter server address appears. Enter the address as "smb://raspberrypi/RootFolder" and run it. Then, a logon message window is displayed and you should use "pi" as your user account.

 

 

   Connecting from Linux

 

To connect to the Raspberry Pi system from Linux, you mount the drive.

 

First, you create the directory to mount the drive. Here "piRootFolder" is used for mounting directory.

 

$ sudo mkdir  /piRootFolder

 

 

The following is the command to mount the "/RootFolder" of the Raspberry Pi system to the "/piRootFolder" folder of Linux system. Once the operation is complete, you can access the data with "/piRootFolder.

 

$ sudo smbmount o username=pi,password=raspberry //192.168.1.202/RootFolder /piRootFolder