1,234
edits
Changes
→Using Nautilus to browse Samba shares
==OBJECTIVE & PREPARATION==
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).
==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:'''
server string = "put your real name here without the quotes"
encrypt passwords = yes
[home]
comment = "put your real name here without the quotes"
printable = no
create mask = 0765
[homes]
comment = automatic home share
public = no
writable = yes
printable = no
create mask = 0765
browseable = no
<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 will be able to access it:</li></ol>
hosts allow = 192.168.x. 127.0.0.1
{{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>Since we If you have SELinux set SELinux to enforcing, we you'll will need to tell it to allow samba access to home directoriesby running: <br> '''setsebool -P samba_enable_home_dirs 1'''</li><li>Use the '''ss -nautp''' command to see with port Samba is running on.</li><li>Use the information in the previous step to modify the firewall on VM2 machine 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
#Install the '''samba-client''' and '''cifs-utils''' packages.
#Use the "smbclient" command in a terminal window.<source>
smbclient '\\vm2\home' -U <learnidyourSenecaID></source>
#After entering your password you should get a prompt similar to:<source>
smb: \></source>
#Once you have access to the directory use the get and put commands (similar to ftp) to move files.
#When you are finished close the connection.
# Try again using '''[homes]''' share instead
<source>
smbclient '\\vm2\homes' -U <yourSenecaID></source>
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. '''The Perform the following steps require a graphical interface; perform them on your HOSTVM1'''
==INVESTIGATION 3: CONNECTING TO A SAMBA SERVER FROM A WINDOWS CLIENT==
# Make certain that your '''VM2''' machine is running, is still allowing samba traffic through the firewall, and is still running the samba service.
# Power up Use the Windows machine you are already running Vmware on. If you have a Linux host - good for you, you can either use a Windows system in the lab and loginVM or skip this part.# Add the prerouting and forwarding rules to your host's iptables necessary to redirect samba traffic from outside your network to your VM 2VM2, making sure to replace the X with your own network address.::<code>iptables -I FORWARD -p tcp --dport 139 -d 192.168.X.3 -j ACCEPT</code>::<code>iptables -I FORWARD -p tcp --dport 445 -d 192.168.X.3 -j ACCEPT</code>::<code>iptables -t nat -A PREROUTING -p tcp --dport 139 -j DNAT --to-destination 192.168.X.3</code>::<code>iptables -t nat -A PREROUTING -p tcp --dport 445 -j DNAT --to-destination 192.168.X.3</code>OR with specifing the interface (whichever works):::<code>iptables -t nat -A PREROUTING -i *externalinterface* -p tcp --dport 139 -j DNAT --to-destination 192.168.X.3</code>::<code>iptables -t nat -A PREROUTING -i *externalinterface* -p tcp --dport 445 -j DNAT --to-destination 192.168.X.3</code>where *externalinterface* is an interface name (e.g. ens33)<br>'''NOTE:''' when you restart libvirtd, it will move your FORWARD rules to the end of the chain, invalidating them.# Modify the '''hosts allow ''' setting on your '''vm2''' to also accept connections from the windows machine you are using.# Open the Windows File Explorer application.# At the top of the application, enter the following:<br>'''\\IPADDR_OF_HOST_MACHINEEXTERNAL_IPADDR_OF_HOST\home'''
{| width="40%" align="right" cellpadding="10"
|}
<ol><li value="5"> You will be prompted to enter your VM2 samba username and password (one time only). Refer to diagram screenshot on right.<br><br>'''NOTE:''' It may take approximately 30 seconds to display the file contents.<br><br></li><li>Where Were you successful? You should have received an error stating the your credentials are incorrect. You will notice that it adds SENEDS to the beginning of your user name, as the Seneca machine is pre-configured to be part of that workgroup.</li><li>Change the workgroup parameter in smb.conf on VM2 to match the seneca domain SENEDS, and try to connect again.</li><li>Were you successful? If not, try to troubleshoot the problem first, then ask your lab assistant or instructor for assistance.</li><li>Close the Windows File Explorer application window.</li><li>Click on the '''START''' menu, and click on '''This PC'''.</li><li>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.</li><li>When finished, click on '''Network''' in Windows file manager to confirm that the network share is present.</li><li>Try to create a file on Windows on your Linux Samba machine. Were you able to create a save a file?</li><li>Switch to your VM2 machine and check to see if that file was created in your home directory.</li></ol>
{{Admon/important |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 or rsync 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'''
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..
::<span style="color:green;font-size:1.5em;">✓</span> Proof of network share of VM2 machine from Windows VM via Windows Explorer application
::<span style="color:green;font-size:1.5em;">✓</span> Display contents of '''/etc/samba/smb.conf''' file on VM2 machine
::<span style="color:green;font-size:1.5em;">✓</span> Firewall exceptions (both machines) to allow Samba traffic
::<span style="color:green;font-size:1.5em;">✓</span>Download the labcheck5.bash checking bash shell script by issuing the command:<br><br>and run '''wget httphttps://matrixict.senecac.onsenecacollege.ca/~peterandrew.callaghan/filessmith/OPS335ops335/labcheck5.bash'''<br><br>set execute permission and run the shell script on your '''c7host''' machine. ::*For '''Peter's classes''', follow his Online Submission instructions in Moodle.::*For '''Murray's classes''', run command (piping to the '''more''' command) and show output to instructor.
::<span style="color:green;font-size:1.5em;">✓</span>Completed Lab5 log-book notes.
-->
==EXPLORATION QUESTIONS==