|
|
| (31 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | [[Category:OPS335]][[Category:OPS335 Labs]]
| + | #REDIRECT [[OPS335_Lab_6]] |
| − | | |
| − | ==SAMBA SERVER RESOURCES==
| |
| − | | |
| − | Online References:
| |
| − | | |
| − | * (Course Notes on Samba Server)
| |
| − | *[http://www.tomsitpro.com/articles/linux-server-configuration-guide-book-excerpt,2-777-2.html 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.
| |
| − | | |
| − | | |
| − | {{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.}}
| |
| − | | |
| − | '''Perform the following steps:'''
| |
| − | | |
| − | #Make certain that both your '''VM1''' and '''VM2''' machines are running. | |
| − | #Switch to your '''VM2''' machine as the '''root''' user.
| |
| − | #Issue the following Linux command to install Samba server utlity:<br>'''yum install samba samba-client'''<br>
| |
| − | #Move the file '''/etc/samba/smb.conf''' to another filename by issuing the following command:<br>'''mv /etc/samba/smb.conf /etc/samba.smb.conf.original'''
| |
| − | #Create a <u>new</u> '''smb.conf''' file that contains the following lines:
| |
| − | [global]
| |
| − | workgroup = <yourSenecaID>.org
| |
| − | 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
| |
| − | <ol><li value="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:</li></ol>
| |
| − | hosts allow = 192.168.x
| |
| − | <ol><li value="4">Append (add) the following parameter to the '''home section''' so that only your user account can access that share:</li></ol>
| |
| − | valid users = <yourSenecaID>
| |
| − | <ol><li value="5">Create a Samba account and password for yourSenecaID by issuing the following command:<br>'''smbpasswd -a <yourSenecaID>'''</li></ol>
| |
| − | | |
| − | {{Admon/tip|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'''.}}
| |
| − | | |
| − | <ol><li value="6">Confirm the user you created has been added using the following command:<br>'''pdbedit -L -v'''</li><li>Test and review your configuration with the command:<br>'''testparm'''</li><li>Use the systemctl command to start the smb.service and enable the service to run on boot-up</li><li>Modify the firewall on VM2 to allow samba traffic.</li><li>Test to see that you can connect to your Samba server (locally) by issuing the following command:<br>'''smbclient -U <yourSenecaID> -L 127.0.0.1'''</li><li>When prompted, enter your Samba account password.</li><li>The output from that issued command show appear similar to example displayed below:</li></ol>
| |
| − |
| |
| − | 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
| |
| − | --------- ------
| |
| − |
| |
| − | <ol><li value="13">To access the Samba client shell on your local Samba share, issue the following command:<br>'''smbclient '\\127.0.0.1\home' -U <yourSenecaID>'''</li><li>Enter your Samba account password.</li><li>Issue the help command to note common commands (dir, cd, ls, put, get). Note how similar they are to sftp commands.</li><li>Enter exit to terminal your local Samba session.</li>
| |
| − | | |
| − | | |
| − | | |
| − | '''Record steps, commands, and your observations in INVESTIGATION 1 in your OPS335 lab log-book'''
| |
| − | | |
| − | ==INVESTIGATION 2: USING A SAMBA SERVER TO SHARE FILES FROM OTHER LINUX SERVERS ==
| |
| − | | |
| − | Although the main purpose of running a samba server is to share files on a Windows server, you can also install a Samba client on another Linux machine to share files as well. This lab will demonstrate how to setup a Samba client on your '''host''' machine, mount the samba share on a directory, and access files on the remote Linux machine ('''vm2''').
| |
| − | | |
| − | === Accessing and Sharing Files on Remote Linux Server (smbclient)===
| |
| − | | |
| − | | |
| − | | |
| − | '''Perform the following steps:'''
| |
| − | | |
| − | #In a full installation (on your host Linux machine) you should not need to install the '''samba-client''' application on your host, but if it is not present, then install that application.
| |
| − | #You will also need to install the ''cifs-utils'' package to be able to mount the filesystem:<br>'''yum install cifs-utils'''
| |
| − | #From the host use the "smbclient" command in a terminal window:<br>'''smbclient '\\vm2\home' -U <learnid>'''
| |
| − | #After entering your password you should get a prompt similar to:<br>'''smb: \>'''
| |
| − | #Enter the ls command to see a list of the files in your home directory:<br>'''smb: \> ls'''<br><br>'''NOTE:''' you may receive the following error: ''NT_STATUS_ACCESS_DENIED listing''<br><br>
| |
| − | #SE Linux should be in Enforcing and will need to be adjusted (on the samba server) for this to work by issuing the command:<br>'''setsebool -P samba_enable_home_dirs 1'''
| |
| − | #Once you have access to the directory use the '''get''' and '''put''' commands (similar to sftp) to move files.
| |
| − | #When you are finished close the connection.
| |
| − | | |
| − | === Mounting a Remote Linux Volume (mount -t cifs) ===
| |
| − | | |
| − | When performing the NFS lab, one of the initial purpose of using NFS was allowing network shares to mount remote volumes as opposed to using '''sftp''' (''get'' and ''put'' commands). This section will demonstrate how to '''mount a remote Linux volume''' as a directory for the client Linux server.
| |
| − | | |
| − | '''Perform the following steps:'''
| |
| − | | |
| − | #Issue the following command to create a mount point called vm2-home:<br>'''mkdir /tmp/vm2-home'''
| |
| − | #Issue the following command in order to mount your home directory:<br>'''mount -t cifs //vm2/home /tmp/vm2-home -o username=<learnid>'''
| |
| − | #Verify that the mount worked by issuing the following command:<br>'''ls /tmp/vm2-home'''
| |
| − | #What is the advantage of using this method as opposed to the smbclient command in the previous section? Record your answer in your lab log-book.
| |
| − | | |
| − | | |
| − | '''Record steps, commands, and your observations in INVESTIGATION 2 in your OPS335 lab log-book'''
| |
| − | | |
| − | ==INVESTIGATION 3: CONNECTING TO A SAMBA SERVER FROM A WINDOWS CLIENT==
| |
| − | | |
| − | This investigation will configure your host machine to access files in a MS Windows server via command line and graphically.
| |
| − | | |
| − | === Creating a Windows 2008 Server 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 Windows 2008 server as a virtual machine.
| |
| − | | |
| − | '''Perform the following steps:'''
| |
| − | | |
| − | #Make certain you are using your '''host''' machine.
| |
| − | #Download a version of MS Windows 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).<br>'''NOTE:''' You cannot use a CD/DVD since KVM does not install by CD/DVD.<br><br>'''ALTERNATIVE METHOD:''' You could also refer to the following link to download any MS Windows OS: https://inside.senecacollege.ca/its/software/ , <br>select '''Software Downloads''', login with your senecaid and password, select '''MSDN''', and then select a Windows OS ISO to download.<br>You are <u>not</u> required to obtain a product key since you will not need to extend the use of this Windows OS over 60 days.
| |
| − | | |
| − | {{Admon/tip |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 <u>administrator</u> (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.}}
| |
| − | | |
| − | | |
| − | <ol><li vaLUE="3">Create a new virtual machine (hard drive size: '''20 GB''', accept all other defaults) making certain to specify the location of your downloaded Windows OS iso file.</li><li>Install the Windows OS creating a default user and administrator.</li><li>Upon successful installation, open the command prompt, and note the '''IPADDR''' for that Windows Machine.</li><li>On your Linux host machine, use the same techniques that you learned in '''INVESTIGATION 2''' to use smbclient and also to '''mount''' (mount -t cifs) the MS Windows files on your '''host''' machine. Were you successful?</li><li>If you were not successful, why do you think was the reason?</li><li>Call over your lab assistant or instructor if you are uable to access your MS Windows files on your Linux host machine.</li></ol>
| |
| − | | |
| − | ===Accessing MS Windows Files from a Graphical Application (nautilus) ===
| |
| − | | |
| − | If you have properly installed smbclient and mounted your MS Windows File Share on your Linux '''host''' machine, you should be able to use your default graphical file manager application (nautilus) to access files on your remote Windows server.
| |
| − | | |
| − | '''Perform the following tasks:'''
| |
| − | | |
| − | #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'''.
| |
| − | #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.
| |
| − | #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'.
| |
| − | | |
| − | === Accessing MS Windows Files via a Graphical Web Browser (konqueror) ===
| |
| − | | |
| − | If your web browser application support the SMB protocol, you can also access files on your remote Windows server by a web browser.
| |
| − | | |
| − | '''Perform the following tasks:'''
| |
| − | #You can also use a web browser with support for the SMB protocol such as Konqueror. Note that firefox does not have such support.
| |
| − | #If Konqueror is not installed then install it with the command:<br>'''yum install kdebase'''
| |
| − | #Start Konqueror, the web/file browser, and in the address bar enter the following:<br>'''smb://vm2/home'''
| |
| − | #Enter your username and password when prompted.
| |
| − | #Double click on a file you have some text in.
| |
| − | #Open it with gedit, make some changes, and save it.
| |
| − | #When prompted, choose to upload the file.
| |
| − | #Close Konqueror.
| |
| − | #cat the file on your VM2 to ensure the changes were properly uploaded.
| |
| − | | |
| − | | |
| − | '''Record steps, commands, and your observations in INVESTIGATION 3 in your OPS335 lab log-book'''
| |
| − | | |
| − | ==COMPLETING THE LAB==
| |
| − | | |
| − | Arrange proof that ...
| |
| − | | |
| − | | |
| − | ==EXPLORATION QUESTIONS==
| |
| − | | |
| − | | |
| − | #What does SMB and CIFS represent?
| |
| − | #What is the purpose of the testparm command?
| |
| − | #What does the text inside square brackets in the smb.conf file mean? (e.g., "[home]").
| |
| − | #Explain the meaning of the line "create mask = 0765" in the smb.conf file?
| |
| − | #What does the smbpasswd command do?
| |
| − | #What did the setsebool command do?
| |
