Open main menu

CDOT Wiki β

OPS335 Lab 6

Revision as of 03:33, 12 July 2016 by Peter.callaghan (talk | contribs) (Using the Windows machines in the lab, not a VM.)


SAMBA SERVER RESOURCES

Online References:

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. 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 = yes
writable = yes
printable = no
create mask = 0765
  1. 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. 127.0.0.1
  1. Append (add) the following parameter to the [home] section so that only your user account can access that share:
valid users = <yourSenecaID>
  1. 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.
  1. Confirm the user you created has been added using the following command:
    pdbedit -L -v
  2. Test and review your configuration with the command:
    testparm
  3. Use the systemctl command to start the smb.service and enable the service to run on boot-up
  4. If you are in one of the sections with SELinux set to enforcing, you will need to tell it to allow samba access to home directories: setsebool -P samba_enable_home_dirs 1
  5. Install the netstat command by issuing the following command:
    yum install net-tools
  6. Issue the netstat -nautp command to see with port Samba is running on.
  7. Use the information in the previous step to modify the firewall on VM2 machine to allow samba traffic.
  8. 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
  9. When prompted, enter your Samba account password.
  10. 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
---------             ------
  1. To access the Samba client shell on your local Samba share, issue the following command:
    smbclient '\\127.0.0.1\home' -U <yourSenecaID>
  2. Enter your Samba account password.
  3. Issue the help command to note common commands (dir, cd, ls, put, get). Note how similar they are to sftp commands.
  4. 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.

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. Power up a Windows system in the lab and login.
  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. Open the Windows Explorer application.
  5. 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).
  1. 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.

  2. Where your successful? If not, try to troubleshoot the problem first, then ask your lab assistant or instructor for assistance.
  3. Close the Windows Explorer application window.
  4. Click on the START menu, and click on Computer.
  5. 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.
  6. When finished, click on Network in Windows file manager to confirm that the network share is present.
  7. Try to create a file on Windows on your Linux Samba machine. Were you able to create a save a file?
  8. Switch to your VM2 machine and check to see if that file was created in your home directory.


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

COMPLETING THE LAB

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
✓ Lab logbook completed


EXPLORATION QUESTIONS

  1. What does SMB?
  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?
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=OPS335_Lab_6&oldid=119066"