932
edits
Changes
m
smb passwd file security = /etc/samba/smbpasswduser passdb backend = tdbsam
→Using 'mount -t cifs'
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
#Install the '''samba-client''' and '''cifs-utils''' packages.
#Use the "smbclient" command in a terminal window.<source>
smbclient '\\vm2\homeshome' -U <yourSenecaID></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>
Did it work even though you didn't specify '''path=/home/<yourSenecaID>''' under '''[homes]'''?<br /><br />
Note that this tool only gave temporary access with a limited set of commands.
Note that this tool would leave the directory mounted until the machine rebooted or it was manually unmounted. It would also allow other users access to the directory, as it effectively became part of the local filesystem. It could even be added to fstab to be mounted on boot (if it didnthough this would require another configuration file we don't need a passwordcover).
=== Using Nautilus to browse Samba shares ===
# Make certain that your '''VM2''' machine is running, is still allowing samba traffic through the firewall, and is still running the samba service.
# If you are using a drive in the removable bay, power up a Windows system in the lab and login. If you are using a USB SSD drive, use VMware to create a new virtual machine in the same network as your host and install Windows machine you are already on it.
# Add the prerouting and forwarding rules to your host's iptables necessary to redirect samba traffic from outside your network to your VM 2.
# 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_MACHINE\home'''
|}
<ol><li value="5"> You will be prompted to enter your VM2 samba username and password (one time only). Refer to diagram 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 command, and you should use the Bash shell script that you were adviced to create in order to backup all of your VMs.}}
