OPS335: File Servers

SAMBA SERVER RESOURCES

Online References:

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

OVERVIEW

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 another virtual machine will be created for a Windows operating system. Finally, within the Windows virtual machine, users will access files from the Linux Samba server (both graphically and command line).

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.

Prerequistites
Due to the changes made in lab3, you will now need your vm1 running (as the DNS server) in order for any of your virtual machines to be able to use the internet.

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. Move the file /etc/samba/smb.conf to another filename by issuing the following command:
   mv /etc/samba/smb.conf /etc/samba.smb.conf.original
5. Create a new smb.conf 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 and those in the lab room will be able to access it:

hosts allow = 192.168.x

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. Modify the firewall on VM2 to allow samba traffic.
10. 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
11. When prompted, enter your Samba account password.
12. 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.

Although you can use smbclient to access, browse and share files within other Linux and Windows servers, it is more practical to setup a Samba server to allow MS Windows Users to access a common file share on a Linux machine, and will be demonstrated in Investigation 2.

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

INVESTIGATION 2: 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.

Creating a Windows7 Professional VM

To demonstrate how to access and share files from a remote MS Windows server using smbclient on your host machine, we will install a Windows7 Professional machine as a virtual machine.

Perform the following steps:

1. Make certain you are using your host machine.
2. Download a version of MS Windows7 Professional ISO file to your host machine. If you have already downloaded an ISO file, then you can use that (i.e. transfer to your host machine).
   NOTE: You cannot use a CD/DVD since KVM does not install by CD/DVD.
   
   ALTERNATIVE METHOD: You could also refer to the following link to download Windows7 OS image: https://inside.senecacollege.ca/its/software/ ,
   select Software Downloads, login with your senecaid and password, select MSDN, and then select a Windows7 Professional iso image to download.
   You are not required to obtain a product key since you will not need to extend the use of this Windows OS over 60 days.

Rearming the Windows Trial Version
If are your trial period for your Windows machine is nearly over, you can extend the trial period for another 30 days by running a command prompt as the administrator (right-click on cmd icon) and issuing the command: slmgr -rearm. Obviously, you are required to perform this operation prior to the termination of the initial trial period.

3. Create a new virtual machine (RAM: 1024 MB, hard drive size: 20 GB, accept all other defaults) making certain to specify the location of your downloaded Windows OS iso file.
4. Install the Windows OS creating a default user as the administrator.
5. Upon successful installation, log into the Windows machine as a regular user, open a command prompt and using the ping command to confirm that you can connect to your VM2 machine.

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 both your VM2 and Windows virtual machines are running.
2. On your Windows VM, temporarily turn off the firewall for your Windows machine.
3. Open the Windows Explorer application.
4. At the top of the application, enter the following:
   \\IPADDR_OF_VM2_MACHINE\home
5. You will be prompted to enter your VM2 username and password (refer to diagram on right).
6. Where your successful?
7. Close Windows Explorer application window.
8. Switch to your VM2 machine.
9. Add the following parameter at the bottom of the [home] section of the /etc/samba/smb.conf file:

browsable = yes

10. Return to your Windows VM and open another Windows explorer application window.
11. # Again, at the top of the application, enter the following:
    \\IPADDR_OF_VM2_MACHINE\home
12. # What happens this time?
<
13. # Switch back to your VM2 machine and install the netstat command on your VM2 machine by issuing the following command:
    yum install net-tools
14. # Issue the netstat -natp command to determine the port number of the Samba connection.
    1. In your Windows machine, modify the firewall setting to make appropriate exception for connecting to Samba from your VM2 machine.

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

COMPLETING THE LAB

Arrange proof that ...

EXPLORATION QUESTIONS

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