1,234
edits
Changes
→Using Nautilus to browse Samba shares
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.
'''Perform the following steps:'''
# Create another virtual Make certain that both your '''VM1''' and '''VM2''' machines are running.#Switch to your '''VM2''' machine called as the '''vm4root''' from scratch (only a minimal setup is needed)user. If you forgot how #Issue the following Linux command to do this, refer to [httpinstall Samba server utlity://zenit.senecac.on.ca/wiki/index.php/OPS335_Installation_Lab#VM_Installation Lab1].<br>'''yum install samba samba-client'''<br>#Copy the file '''For Interest:/etc/samba/smb.conf''' As an optional exerciseto another filename by issuing the following command: configure all your network settings (except the firewall) using the installation wizard during installation static IP<br>(the address '''192cp /etc/samba/smb.168conf /etc/samba/smb.Xconf.5original'''#Clear the contents of the configuration file by running ''' should be available)cat /dev/null > /etc/samba/smb.<br><br>conf'''# Configure your Edit '''vm4/etc/samba/smb.conf''' virtual machine in so that the same way file that you've configured contains the other three main VMs. This should be a quick exercise for you by now, includingfollowing lines:::* The Linux installation [global] workgroup = WORKGROUP server string = "put your real name here without the quotes" encrypt passwords = yes security = user passdb backend = tdbsam [home] comment = "put your real name here without the quotes" path = /home/<yourSenecaID> public = no writable = yes 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 (minimum installadd)::* If you didn't setup the network configuration during installation, make certain following parameter to connect the bottom of the '''[global] section''' that will limit access to the correct share so that only machines in your virtual network with a static IPwill be able to access it:</li><br/ol>(the address hosts allow = 192.168.Xx. 127.0.0.5 should be available),1::* Making sure you're using your internal DNS server <ol><li value="4">Append (make reference add) the following parameter to vm4's IPADDR for domain resolution)::* Configuring default rules for your iptables firewall (hint: use saved shell scripts)::* Allowing passwordless login from the host's root account (for future backups)::* Disabling ''[home] section'selinux''' since you don't know how to configure it properly.so that only your user account can access that share:</li><br/ol> valid users = <bryourSenecaID><ol><li value="35">Test your Create a Samba account and password for yourSenecaID by issuing the following command:<br>'''vm4smbpasswd -a <yourSenecaID>''' virtual machine to make certain that it functions correctly.</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=== Install"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>If you have SELinux set to enforcing, you'll will need to tell it to allow samba access to home directories by 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, Configure & Run a Webserver 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 (Apache"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></ol>
'''Perform the following Record steps:''' #Make certain you are in your '''VM4''' machine.#Install the Apache package (the name of the package is: '''httpd''').#Start the httpd service, commands, and enable this service to start automatically upon system startup.#Make certain to configure your firewall to allow access to the httpd service (i.e. the Apache serves HTTP traffic which goes over TCP port '''80''').#Open a web-browser in your '''host''' machine and enter the following URL: '''vm4.youruserid.org'''.<br>If you setup your Apache webserver correctly, you should be able to view the Apache Test page.#Delete the file '''/etc/httpd/conf.d/welcome.conf''' to remove the default webpage.#Although we will not be exploring webservers observations in depth, we will have you create a simple webpage for testing purposes, then later setup a web resource for webmail.#The term'''DocumentRoot''' specifies where the Apache webserver will search for documents to serve. Create the file '''index.html''' INVESTIGATION 1 in your OPS335 lab log-book'''DocumentRoot''' directory with the following contents (replace the date with the current one):
=== Installing and Using smbclient ===
'''Perform the following steps on your VM1'''
#Issue the following commands to create a mount-point and to mount your home directory from your vm2 machine:<presource>Hello, this is a web page on vm4.yourid.org and the current time is mkdir /tmp/vm2-home mount -t cifs //vm2/home /tmp/vm2-home -o username=<?php system("date"); ?yourSenecaID>! ls /tmp/vm2-home</presource>#Create a file in that directory, then switch to '''vm2''' to confirm that it was created.#Use umount on '''vm1''' to unmount that directory.
# Make certain that your '''VM2''' machine is running, is still allowing samba traffic through the firewall, and is still running the samba service.# 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 VM 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 VM2, 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* $config['smtp_server']-p tcp --dport 139 -j DNAT --to-destination 192.168.X.3</code>::<code>iptables -t nat -A PREROUTING -i * $config[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''default_host']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::* $config[<br>'''\\EXTERNAL_IPADDR_OF_HOST\home''default_port']
|- valign="top"
|
[[Image:samba-login.png|thumb|right|300px|You will be prompted (once only) for the Samba user-name and password for your '''VM2''' machine). ]]
|
[[Image:samba3-map-drive.png|thumb|right|300px|You can create a '''mapped network drive (z:)''' for your Linux Samba server network share). ]]
|}
<ol><li value="45">You will be prompted to enter your samba username and password (one time only). Refer to screenshot on right.<br><br>'''NOTE:''' It may take approximately 30 seconds to display the file contents.<br><br></li><li>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 test the configuration create a save a file?</li><li>Switch to your VM2 machine and check to see if that file was created in your Roundcube installer Step 3home directory.</li></ol>
{{Admon/important |Backup your VMs!|You MUST perform a '''full backup'''Record steps, commands, and of ALL of your observations in INVESTIGATION 2 in VMs whenever you complete your '''OPS335 labs''' or when working on your '''OPS335 lab log-bookassignments'''. You should be using the dump or rsync command VMs.}}
'''Record steps, commands, and your observations from this INVESTIGATION in your OPS335 lab log-book'''
== COMPLETING THE LAB ==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> Firewall settings on your Windows VM to allow Linux Samba network share
::<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 and run '''https://ict.senecacollege.ca/~andrew.smith/ops335/labcheck5.bash'''
::<span style="color:green;font-size:1.5em;">✓</span>Completed Lab5 log-book notes.
-->
==EXPLORATION QUESTIONS==
#What does SMB stand for?#What does CIFS stand for?#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?