[[Category:OPS335]][[Category:OPS335 Labs]]
==FILE SAMBA SERVER RESOURCES==
Online References:
*[https://prezi.com/sfxdbjbxgu1e/file-servers-nsf-samba/ File Server Notes] (Week 9 class notes)*[http://tldp.org/HOWTO/NFS-HOWTO/security.html NSF Security] (List of tips regarding NSF and security)x
==OVERVIEW==
In '''OPS235''', you learned how to install and configure an SSH server to be able to use utilities such as '''ssh''', '''scp''' and '''sftp'''. Although the '''sftp''' utility is useful for transferring files between different computers via the Internet, it is not considered useful or efficient for accessing files on servers that are connected over a local network.x
Two popular protocols called '''Network File Server''' ('''NFS''') and '''Samba''' ('''SMB''') are used to provide high speed file access between servers on a local network. The '''NFS''' protocol allows a user to access files on another server in a local network in a similar way that local files on a same server are accessed. The '''Samba''' open-source software is used to access files from Windows servers using a combination of Windows protocols including NetBIOS, SMB, etc.==INVESTIGATION 1: INSTALLING & CONFIGURING A SAMBA SERVER==
This lab will focus on installing, configuring and using '''NFS''' and '''Samba''' to access files between different servers on a local network. ==INVESTIGATION 1: USING AUTOMOUNT WITH '''NFS'''== In this investigation, we will set up an a '''NFS Samba server''' on our '''VM2''' machine. We will then set up an '''NFS client''' on our '''VM3''' machine and be able to view and '''import files''' within the VM2 /home directories from the VM3 machine. {{Admon/important|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.}} ===Setting up the NFS Server (VM2)=== '''Perform the following tasks:''' #Make certain that all of your VMs are running.#Switch to your '''VM2''' machine.#Although nsf is already on your VM when you installed it, we will install additional utilities for nsf. Issue the following command:<br>'''yum install nfs-utils'''#The '''/etc/exports''' file allows you to restrict the access to servers to access files for security purposes. Edit '''/etc/exports''' file, and replace all contents of the file with the following:<br>'''/home 192.168.x.4(rw,root_squash,insecure)'''#Start enable your nfs service (now known as '''nfs-server.service''').#Build the server's list of exports: <br>'''exportfs -r'''#Run and record the output of the following commands:<br>'''exportfs'''<br>'''showmount -e'''#You will have to adjust your firewall settings on your VM2 machine to allow NFS to work.<br>Run the '''netstat''' command in order to determine the ports needed and issue the appropriate ''iptables'' command(s). ===Setting up & Testing the NFS Client (VM3)=== '''Perform the following tasks:''' #Ensure the VM guest network is functioning properly. You can use the "host cbc.ca" command to see if DNS queries are being answered. #Ensure you have full connectivity to the internet.#Again, you should not have to install any NFS software.#Add the following line to the bottom of the '''/etc/fstab''' file on your VM3 machine:<br>'''192.168.x.3:/home /home nfs4 defaults 0 0'''{{Admon/important|Warning:|Do not change any other lines in +++Complete this file. Do not change any lines in /etc/fstab on your host machine. Doing so can make your machine fail to boot.}}<ol><li value="5">Run the following command to avoid an error that would be caused by logging in while root_squash is active:<br>'''setsebool -P'''<br>'''use_nfs_home_dirs 1'''</li><li>Logout of vm03 and shut it down.</li><li>Restart vm03 and login using your learnid.</li><li>Check that the home directory is mounted:<br>'''mount | grep /home'''</li><li>If it is not, try running 'mount /home' as root and observe any errors.</li><li>On vm03, create an empty file by issuing the following command:<br>'''touch empty_file_created_on_vm03'''</li><li>Now shutdown vm03.</li><li>Now on the NFS server, us ls -l in your learnid's home directory to check for the file you just created.</li></ol>sentence +++
===Setting up Automount (VM3)===
'''Perform the following tasks:'''
#Switch to your VM3 machine.
#Comment or remove the line from /etc/fstab that you entered earlier.
#With a server installation of Fedora 22, you will not need to install autofs, but on other installations you might need:<br>'''dnf install autof'''s
#Move the existing file /etc/auto.master:<br>'''mv /etc/auto.master /etc/auto.master.orig'''
#This is a great way to keep a back up in case you need to restore the file in the future. Now create another:<br>'''vi /etc/auto.master'''
#Add only the following line:<br>'''/home /etc/auto.home --timeout=60'''
#Create the file /etc/auto.home and add ONLY the following line:<br>'''* -fstype=nfs4,rw,nosuid,soft 192.168.x.3:/home/&'''
#Start autofs, and ensure the service will automatically start at boot.
#Log out of vm3 and log back in using your learn account.
#Open a terminal and enter the command:<br>'''mount | grep home'''
#How does it differ from the previous mount?
#Create another empty file with the name:<br>'''touch another_empty_file_from_vm03'''
#Run and record the output of the command:<br>'''df -hT'''
#Back on the nfs server run and record the output of ls -l in your home directory.
#You should see the files you created on vm03.
#You may encounter errors with SELinux during the lab (though it has not been a problem recently). It is required that you leave it running. #Use the following commands to determine what booleans need to be flipped:<br>'''audit2allow < /var/log/audit/audit.log'''<br>'''audit2why < /var/log/audit/audit.log'''
#Now that you have VM3 automatically mounting home directories from VM2, configure VM1 to do the same.
'''Record steps, commands, and your observations in INVESTIGATION 1 in your OPS335 lab log-book'''
==INVESTIGATION 2: USING '''SAMBA''' TO ACCESS FILES ON WINDOWS SERVERS==
In this investigation, we will set up a '''Samba server''' on our '''VM2''' machine. +++Complete this sentence +++
===Installing & Configuring a Samba Server on Linux===
*On your VM 2 install Samba
dnf install samba samba-client
*It will show you a list of all available shares.
===Connecting to a Linux SMB Server from a Linux Client=INVESTIGATION 2: CONNECTING TO A LINUX SAMBA SERVER FROM A LINUX CLIENT==
There are many ways that a Linux client can connect to an SMB server.
==== Using smbclient ====
*In a full installation you should not need to install samba-client on your host, but if it is not present then do so.
*You will also need to install the cifs-utils package to be able to mount the filesystem.
*When you are finished close the connection.
==== Using 'mount -t cifs' ====
*The next way is to use the mount command.
*Use the mount command on the host to mount your home directory
ls /tmp/vm2-home
==== Using Nautilus to browse Samba shares ====
*Use the "Places" menu from the desktop and open 'Browse Network'.
*From the menu in the side-bar of the files tool, choose 'Connect to Server'.
*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'.
==== Using a browser ====
*You can also use a web browser with support for the SMB protocol such as Konqueror.
**Note that firefox does not have such support.
*cat the file on your VM2 to ensure the changes were properly uploaded.
====Connecting to a Linux SMB Server from a Windows Client (Windows 7)==INVESTIGATION 3: CONNECTING TO A SAMBA SERVER FROM A WINDOWS CLIENT==*Power up a Windows 7 system in the lab and login using your LEARN username and password.*Add the prerouting and forwarding rules to your Centos host's iptables necessary to redirect samba traffic from outside your network to your VM 2.*Open up Explorer and Right click on Computer > Map network drive.. > Select a Drive Letter and '\\<ip-address-of-host>\home' > you will then be asked for your username and password.*You should now be able to browser, drag and drop your files to and from the Windows machine. New procedures
