OPS335 Lab 5

OBJECTIVE & PREPARATION

According to the samba.org website:

"Samba is the standard Windows interoperability suite of programs for Linux and Unix. Samba is Free Software licensed under the GNU General Public License, the Samba project is a member of the Software Freedom Conservancy."

Although a Samba server can provide many features such as printer sharing and backups, this lab's primary focus is to set up a Samba server on a Linux server in order to allow MS Windows users to share common files from the Linux's Samba server.

This lab will first install, setup, and enable a Samba server. Then users will access files on the Linux Samba server from Linux and Windows client machines (both graphically and command line).

Online Resources

• (Course Notes on Samba Server)
• Samba Server Setup (Simple setup guide for samba server]

INVESTIGATION 1: INSTALLING & CONFIGURING A SAMBA SERVER

In this investigation, we will set up a Samba server on our VM2 machine. We will first install, configure and enable the samba server on our virtual machine, and then we will quickly test to see if the Samba server works.

Perform the following steps:

1. Make certain that both your VM1 and VM2 machines are running.
2. Switch to your VM2 machine as the root user.
3. Issue the following Linux command to install Samba server utlity:
   yum install samba samba-client
   
4. Copy the file /etc/samba/smb.conf to another filename by issuing the following command:
   cp /etc/samba/smb.conf /etc/samba/smb.conf.original
5. Clear the contents of the configuration file by running cat /dev/null > /etc/samba/smb.conf
6. Edit /etc/samba/smb.conf so that the file that contains the following lines:

[global]
workgroup = WORKGROUP 
server string = "put your real name here without the quotes"
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
  
[home]
comment = "put your real name here without the quotes"
path = /home/<yourSenecaID>
public = no
writable = yes
printable = no
create mask = 0765

3. Append (add) the following parameter to the bottom of the [global] section that will limit access to the share so that only machines in your virtual network will be able to access it:

hosts allow = 192.168.x. 127.0.0.1

4. Append (add) the following parameter to the [home] section so that only your user account can access that share:

valid users = <yourSenecaID>

5. Create a Samba account and password for yourSenecaID by issuing the following command:
   smbpasswd -a <yourSenecaID>

Changing Existing Samba Account Passwords
If you need to change a user's existing Samba account password, you can issue the following command as root: smbpasswd username.

6. Confirm the user you created has been added using the following command:
   pdbedit -L -v
7. Test and review your configuration with the command:
   testparm
8. Use the systemctl command to start the smb.service and enable the service to run on boot-up
9. Since we set SELinux to enforcing, we will need to tell it to allow samba access to home directories: setsebool -P samba_enable_home_dirs 1
10. Use the ss -nautp command to see with port Samba is running on.
11. Use the information in the previous step to modify the firewall on VM2 machine to allow samba traffic.
12. Test to see that you can connect to your Samba server (locally) by issuing the following command:
    smbclient -U <yourSenecaID> -L 127.0.0.1
13. When prompted, enter your Samba account password.
14. The output from that issued command show appear similar to example displayed below:

Sharename       Type       Comment
---------       ----       -------
home             Disk      Your Name
IPC$             IPC       IPC Service ("Your Name")
Domain=[WORKGROUP] OS=[Windows 6.1] Server=[Samba 4.2.3]

Server                Comment
------                -------

WorkGroup             Master
---------             ------

13. To access the Samba client shell on your local Samba share, issue the following command:
    smbclient '\\127.0.0.1\home' -U <yourSenecaID>
14. Enter your Samba account password.
15. Issue the help command to note common commands (dir, cd, ls, put, get). Note how similar they are to sftp commands.
16. Enter exit to terminal your local Samba session.

You can use smbclient to access, browse and share files within other Linux and Windows servers using a variety of tools which will be demonstrated in Investigations 2 and 3.

Record steps, commands, and your observations in INVESTIGATION 1 in your OPS335 lab log-book

INVESTIGATION 2: CONNECTING TO A LINUX SMB SERVER FROM A LINUX CLIENT

In this investigation you will explore some of the different ways to access a shared directory from a Linux client machine (VM1).

Installing and Using smbclient

Perform the following steps on your VM1

1. Install the samba-client and cifs-utils packages.
2. Use the "smbclient" command in a terminal window.

    smbclient '\\vm2\home' -U <yourSenecaID>

3. After entering your password you should get a prompt similar to:

    smb: \>

4. Enter the ls command to see a list of the files in your home directory:

    smb: \> ls

5. Once you have access to the directory use the get and put commands (similar to ftp) to move files.
6. When you are finished close the connection.

Note that this tool only gave temporary access with a limited set of commands.

Using 'mount -t cifs'

Instead of always having to use the smbclient command to connect to your network share, you can have the share automatically mounted upon your file server boot-up.

Perform the following steps on your VM1

1. Issue the following commands to create a mount-point and to mount your home directory from your vm2 machine:

    mkdir /tmp/vm2-home
    mount -t cifs //vm2/home /tmp/vm2-home -o username=<yourSenecaID>
    ls /tmp/vm2-home

2. Create a file in that directory, then switch to vm2 to confirm that it was created.
3. Use umount on vm1 to unmount that directory.

Note that this tool would leave the directory mounted until the machine rebooted or it was manually unmounted. It would also allow other users access to the directory, as it effectively became part of the local filesystem. It could even be added to fstab to be mounted on boot (if it didn't need a password).

Using Nautilus to browse Samba shares

Instead of accessing your file share via CLI, you can also connect, navigate and access your file share via a graphical application such as a file browser or a web-browser.

Perform the following steps on your HOST machine:

1. Install the samba-client and cifs-utils packages.
2. Use the "Places" menu from the desktop and open 'Browse Network'.
3. From the menu in the side-bar of the files tool, choose 'Other Locations'.
4. In the bar titled 'Connect to Server' enter smb://vm2/home as the location, and enter your samba password in the prompt
   (Where vm2 is the name of the server, and home is the name of the directory it is sharing).
5. After you have checked that you can access your files, unmount the share by right-clicking its icon in the side-bar and clicking 'Unmount'.

You can also use a web browser with support for the SMB protocol such as Konqueror (Note that firefox does not have such support)

6. If Konqueror is not installed then install it with the command:

    yum install kdebase

7. Start Konqueror, the web/file browser, and in the address bar enter the following:
   smb://vm2/home
8. Enter your username and password when prompted.
9. Double click on a file you have some text in.
10. Open it with gedit, make some changes, and save it.
11. When prompted, choose to upload the file.
12. Close Konqueror.
13. cat the file on your VM2 to ensure the changes were properly uploaded.

Record steps, commands, and your observations from this INVESTIGATION in your OPS335 lab log-book

INVESTIGATION 3: CONNECTING TO A SAMBA SERVER FROM A WINDOWS CLIENT

This investigation will configure your VM2 machine to act as a Samba File server to allow Windows OS Users access to the Linux Samba server files.

Accessing Files on a Linux Samba Server via Windows Explorer

With some additional "tweaking" to your Linux Samba server configuration file, you should be able to access files on that file from a Windows machine on the same network. You will be creating a Samba share for your home directory of your regular user account.

Perform the following tasks:

1. Make certain that your VM2 machine is running, is still allowing samba traffic through the firewall, and is still running the samba service.
2. If you are using a drive in the removable bay, power up a Windows system in the lab and login. If you are using a USB SSD drive, use VMware to create a new virtual machine in the same network as your host and install Windows on it.
3. Add the prerouting and forwarding rules to your host's iptables necessary to redirect samba traffic from outside your network to your VM 2.
4. Modify the hosts allow setting on your vm2 to also accept connections from the windows machine you are using.
5. Open the Windows Explorer application.
6. At the top of the application, enter the following:
   \\IPADDR_OF_HOST_MACHINE\home

You will be prompted (once only) for the Samba user-name and password for your VM2 machine).

You can create a mapped network drive (z:) for your Linux Samba server network share).

5. You will be prompted to enter your VM2 username and password (one time only). Refer to diagram on right.
   
   NOTE: It may take approximately 30 seconds to display the file contents.
   
   
6. Where your successful? If not, try to troubleshoot the problem first, then ask your lab assistant or instructor for assistance.
7. Close the Windows Explorer application window.
8. Click on the START menu, and click on This PC.
9. Click on the Map Network Drive button, and create a mapped network drive (called it drive Z:) which is a Samba share of your VM2 machine for the home directory.
10. When finished, click on Network in Windows file manager to confirm that the network share is present.
11. Try to create a file on Windows on your Linux Samba machine. Were you able to create a save a file?
12. Switch to your VM2 machine and check to see if that file was created in your home directory.

Backup your VMs!
You MUST perform a full backup of ALL of your VMs whenever you complete your OPS335 labs or when working on your OPS335 assignments. You should be using the dump command, and you should use the Bash shell script that you were adviced to create in order to backup all of your VMs.

Record steps, commands, and your observations from this INVESTIGATION in your OPS335 lab log-book

COMPLETING THE LAB

In completing this lab you have gained experience using a service that allows remote access to files stored on a Linux server. You have also learned how to use several different tools to access those files, both from a Linux and Windows client..

Depending on your professor you will either be asked to submit the lab in class, or online. Follow the appropriate set of instructions below.

Online Submission (Peter Callaghan's Classes only)

Follow the instructions for lab 5 on blackboard.

In Class Submission (Murray Saul's Classes only)

Arrange evidence (command output) for each of these items on your screen, then ask your instructor to review them and sign off on the lab's completion:

✓ Proof of network share of VM2 machine from Windows VM via Windows Explorer application

✓ Firewall settings on your Windows VM to allow Linux Samba network share

✓ Display contents of /etc/samba/smb.conf file on VM2 machine

✓ Firewall exceptions (both machines) to allow Samba traffic

✓Download the labcheck5.bash checking bash shell script by issuing the command:

wget http://matrix.senecac.on.ca/~peter.callaghan/files/OPS335/labcheck5.bash

set execute permission and run the shell script on your host machine.

• For Peter's classes, follow his Online Submission instructions in Moodle.
• For Murray's classes, run the bash script on host and vm2 (piping to the more command) and show output to instructor.

✓Completed Lab5 log-book notes.

EXPLORATION QUESTIONS

1. What does SMB stand for?
2. What does CIFS stand for?
3. What is the purpose of the testparm command?
4. What does the text inside square brackets in the smb.conf file mean? (e.g., "[home]").
5. Explain the meaning of the line "create mask = 0765" in the smb.conf file?
6. What does the smbpasswd command do?