MountWindowsSharesPermanently
|
Size: 11010
Comment: fixed typo (duplicate _netdev)
|
Size: 8997
Comment: meant to load to community wiki
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from Samba ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| This document describes how to mount CIFS shares permanently. The shares might be hosted on a Windows computer/server, or on a Linux/UNIX server running [[https://help.ubuntu.com/community/Samba|Samba]]. This document also applies to SMBFS shares, which are similar to CIFS but are deprecated and should be avoided if possible ([[https://bugzilla.samba.org/show_bug.cgi?id=1920#c0|link]]). (This document does ''not'' describe how to host the shares yourself, only how to access shares that are hosted somewhere else. For hosting shares, use [[https://help.ubuntu.com/community/Samba|Samba]].) = Prerequisites = We're assuming that: * Network connections have been configured properly. * Your local (Ubuntu) username is ''ubuntuusername''. * Share username on Windows computer is ''msusername''. * Share password on Windows computer is ''mspassword''. * The Windows computer's name is ''servername'' (this can be either an IP address or an assigned name). * The name of the share is ''sharename''. * You want to mount the share in ''/media/windowsshare''. = CIFS installation = {{{ sudo apt-get install cifs-utils }}} On older systems: {{{ sudo apt-get install smbfs }}} = Mounting unprotected (guest) network folders = First, let's create the mount directory. You will need a separate directory for each mount. {{{ sudo mkdir /media/windowsshare }}} Then edit your /etc/fstab file (with root privileges) to add this line: {{{ //servername/sharename /media/windowsshare cifs guest,uid=1000,iocharset=utf8 0 0 }}} Where * '''guest''' indicates you don't need a password to access the share, * '''uid=1000''' makes the Linux user specified by the id the owner of the mounted share, allowing them to rename files, * '''iocharset=utf8''' allows access to files with names in non-English languages. This doesn't work with shares of devices like the Buffalo Tera Station, or Windows machines that export their shares using ISO8895-15. * If there is any '''space in the server path''', you need to replace it by \040, for example //servername/My\040Documents After you add the entry to /etc/fstab type: {{{ sudo mount -a }}} This will (re)mount all entries listed in /etc/fstab. = Mount password protected network folders = The quickest way to auto-mounting a password-protected share is to edit /etc/fstab (with root privileges), to add this line: {{{ //servername/sharename /media/windowsshare cifs username=msusername,password=mspassword,iocharset=utf8,sec=ntlm 0 0 }}} This is not a good idea however: /etc/fstab is readable by everyone and so is your Windows password in it. The way around this is to use a credentials file. This is a file that contains just the username and password. Using a text editor, create a file for your remote servers logon credential: {{{ gedit ~/.smbcredentials }}} Enter your Windows username and password in the file: {{{ username=msusername password=mspassword }}} Save the file, exit the editor. Change the permissions of the file to prevent unwanted access to your credentials: {{{ chmod 600 ~/.smbcredentials }}} Then edit your /etc/fstab file (with root privileges) to add this line (replacing the insecure line in the example above, if you added it): {{{ //servername/sharename /media/windowsshare cifs credentials=/home/ubuntuusername/.smbcredentials,iocharset=utf8,sec=ntlm 0 0 }}} Save the file, exit the editor. Finally, test the fstab entry by issuing: {{{ sudo mount -a }}} If there are no errors, you should test how it works after a reboot. Your remote share should mount automatically. == Special permissions == If you need special permission (like chmod etc.), you'll need to add a ''uid'' (short for 'user id') or ''gid'' (for 'group id') parameter to the share's mount options. {{{ //servername/sharename /media/windowsshare cifs uid=ubuntuuser,credentials=/home/ubuntuuser/.smbcredentials,iocharset=utf8,sec=ntlm 0 0 }}} == Mount password protected shares using libpam_mount (Ubuntu 9.04) == In addition to the initial assumptions, we're assuming that * '''Your username and password are the same on the Ubuntu machine and on the network drive.''' Install libpam-mount: {{{ sudo apt-get install libpam-mount }}} Edit /etc/security/pam_mount.conf.xml using your preferred text editor. {{{ gksudo gedit /etc/security/pam_mount.conf.xml }}} First, we're moving the user specific config bits to a file which users can actually edit themselves: remove the commenting tags (<!-- and -->) surrounding the section called <luserconf name=".pam_mount.conf.xml" />. Save the file when done. With this in place, users can create their own ~/.pam_mount.conf.xml. {{{ gedit ~/.pam_mount.conf.xml }}} Add the following: {{{ <?xml version="1.0" encoding="utf-8" ?> <pam_mount> <volume options="uid=%(USER),gid=100,dmask=0700" user="*" mountpoint="/media/windowsshare" path="sharename" server="servername" fstype="cifs" /> </pam_mount> }}} = Troubleshooting = == Login errors == If you get the error "mount error(13) permission denied", then the server denied your access. Here are the first things to check: * Are you using a valid username and password? Does that account really have access to this folder? * Do you have whitespace in your credentials file? It should be {{{password=mspassword}}}, not {{{password = mspassword}}}. * Do you need a domain? For example, if you are told that your username is {{{SALES\sally}}}, then actually your username is {{{sally}}} and your domain is {{{SALES}}}. The fstab entry should read: {{{...username=sally,password=pass,domain=SALES,...}}} Or: {{{...credentials=/path/to/file,domain=SALES,...}}} * Is the security setting correct? The most common is {{{sec=ntlm}}}, but you can also try the other options listed at the [[http://manpages.ubuntu.com/manpages/raring/en/man8/mount.cifs.8.html|mount.cifs man page]]. The man page list leaves out the option {{{sec=lanman}}} for some reason, but you should try that one as well ([[https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1113395|see discussion]]). == Unprotected network folder won't automount == I've had a situation where an unprotected network folder wouldn't automount during bootup, but after manually entering "sudo mount -a" was mounted correctly. I solved this by replacing the "guest" option by "username=guest,password=". If anyone has an explanation for this, please leave a comment. {{{ //servername/sharename /media/windowsshare smbfs username=guest,password=,uid=1000,iocharset=utf8,codepage=unicode,unicode 0 0 }}} == Mount during login instead of boot == If for some reason/etc/rc0.d/S31umountnfs.sh (networking problems for example) the automatic mounting during boot doesn't work, you can add the "noauto" parameter to your smbfs fstab entry and then have the share mounted at login. In /etc/fstab: {{{ //servername/sharename /media/windowsshare cifs noauto,credentials=/home/ubuntuusername/.smbpasswd 0 0 }}} In /etc/rc.local: {{{ #!/bin/sh -e mount /media/windowsshare exit 0 }}} == Slow shutdown due to a CIFS/Network Manager bug == If you use Network Manager, and are getting really slow shutdowns, it's probably because NM shuts down before unmounting the network shares. That will cause CIFS to hang and wait for 60 seconds or so. Here's how to fix it:/etc/rc0.d/S31umountnfs.sh {{{ sudo ln -s /etc/init.d/umountnfs.sh /etc/rc0.d/K14umountnfs.sh sudo ln -s /etc/init.d/umountnfs.sh /etc/rc6.d/K14umountnfs.sh }}} Ubuntu 12.04 already runs '''umountnfs.sh''' at reboot and shutdown by default (/etc/rc0.d/S31umountnfs.sh and /etc/rc6.d/S31umountnfs.sh) so this is no longer necessary. |
|
| Line 2: | Line 188: |
| [[MountSAMBAshareFSTAB]] ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents(2)>>|| This page is being developed to fix a dead link on the InternetAndNetworking page. = Introduction = This guide will show you how to setup a mount of a remote windows share, and have it always there when you startup. == Two methods, depending on share host == * cifs * smbfs smbfs is the "original" method. However, smbfs is not compatible with security signatures, which are enabled by default and not recommended to disable on Windows Server 2003 and later. If a share is served by Windows Server 2003 or later, you should use cifs. = Prerequisites = You must have a windows machine (or other machine running Samba) with an accessible share. The 'samba' package itself is not necessary if you only need a smb client. The package providing the tools needed to mount "smbfs" and "cifs" filesytems is "smbfs" (up to 10.04) or "cifs-utils" (10.10 onwards). You may have smbfs installed on your machine. If not, run {{{ sudo apt-get install smbfs }}} ...or... {{{ sudo apt-get install cifs-utils }}} ...as appropriate. Update the unmount order to prevent CIFS from hanging during shutdown. {{{ sudo update-rc.d -f umountnfs.sh remove sudo update-rc.d umountnfs.sh stop 15 0 6 . }}} = Setup = == Single User == Note the UID of the single user which is to have access to the share. For a user named $username, the following command outputs the UID {{{ grep $USER /etc/passwd | cut -d: -f3 }}} == Multiple Users == If multiple users are to have the same level of access to the share, then create a new user group, presumably named after the share. Navigate to "System" -> "Administration" -> "Users and Groups" -> "Manage Groups". -> "Add Group" and select a name, Group ID (GID), and group members. Note the GID -- you will need it later. == Credentials File == Warning- this method is not completely secure, any user with root access could see your password in plain text. Create a file called .smbcredentials, probably in the home directory of the primary user of the share. In this file put username an equals sign and the windows username (and domain if loging into a domain) on the first line, put password an equals sign and the password for that user account on the second line of the file. The file should look like: {{{ username=MyUsername password=MyPassword # OR: # username=MyUsername@MyDomain # password=MyPassword # OR: (for cifs on Windows Serve 2003) # username=MyDomain/MyUsername # password=MyPassword }}} On the command line, in the directory of .smbcredentials type {{{ sudo chown root .smbcredentials sudo chmod 600 .smbcredentials }}} this will ensure that only root can access this file. '''''Note:''' Regretfully as from version 3.3.2-1ubuntu3.2 (October 2009) this approach is no longer possible together with the "user" option. A security fix prevents reading the credentials file if you don't have read access to it. You will have to pin the packages at version 3.3.2-1ubuntu3 or 3.3.2-1ubuntu3.1 to continue using this approach as non-root.'' == Editing fstab == Warning- editing the fstab file can be dangerous, please back it up before continuing. Note: if servername or sharename has a literal space (i.e. ' '), substitute \040 instead, so that 'server name' becomes 'server\040name' Add a line at the bottom of your /etc/fstab file that specifies: //$SERVER/$SHARE $MOUNTPOINT $FS_TYPE credentials=$SMB_CREDENTIALS,uid=$UID,gid=$GID {{{ # e.g. SERVER=apollo SHARE=install_files MOUNTPOINT=/path/to/mnt FS_TYPE=smbfs SMB_CREDENTIALS=/path/to/.smbcredentials UID=1000 GID=1000 }}} === smbfs, group permissions === * FS_TYPE=smbfs * GID=1234 # the newly created group's ID * don't include uid=$UID, which defaults to that of root {{{ //apollo/install_files /path/to/mnt smbfs iocharset=utf8,credentials=/path/to/.smbcredentials,gid=1234 0 0 }}} Note: many directories are set so that only the user can write to the directory and that the group can only read (permissions 0755), if this is the case then when it is mounted the group will still not be able to write to the directory regardless of their permission on the share. To give the group write permissions on the mount then use the following. {{{ //apollo/install_files /path/to/mnt smbfs iocharset=utf8,credentials=/path/to/.smbcredentials,dir_mode=0775,gid=1234 0 0 }}} === smbfs, user permissions === * FS_TYPE=smbfs * UID=1000 # particular user's uid * don't include gid=$GID, which defaults to $UID {{{ //apollo/install_files /path/to/mnt smbfs iocharset=utf8,credentials=/path/to/.smbcredentials,uid=1000 0 0 }}} === cifs, group permissions === * FS_TYPE=cifs * GID=1234 # the newly created group's ID * don't include uid=$UID {{{ //apollo/install_files /path/to/mnt cifs iocharset=utf8,credentials=/path/to/.smbcredentials,gid=1234,_netdev 0 0 }}} Note: many directories are set so that only the user can write to the directory and that the group can only read (permissions 0755), if this is the case then when it is mounted the group will still not be able to write to the directory regardless of their permission on the share. To give the group write permissions on the mount then use the following. {{{ //apollo/install_files /path/to/mnt cifs iocharset=utf8,credentials=/path/to/.smbcredentials,dir_mode=0775,gid=1234,_netdev 0 0 }}} === cifs, user permissions === * FS_TYPE=cifs * UID=1000 # the user's uid * don't include gid=$GID {{{ //apollo/install_files /path/to/mnt cifs iocharset=utf8,credentials=/path/to/.smbcredentials,uid=1000,_netdev 0 0 }}} Note: The _netdev option tells the system to wait for the network to become active before attempting to mount. == Ensure == * The entire expression MUST all be on one line in your fstab file * use "//" and "/" instead of "\\" and "\" when specifying the share location * /path/to/mnt is a directory that exists (and is empty) == Completing Setup == Reload fstab: {{{ sudo mount -a }}} = Troubleshooting = == cifs will not mount == Note:- cifs by default does not resolve netbios names so you may get an error message when you try to mount that the name could not be resolved into an address and "could not find target server". In order to enable netbios resolution you need to edit /etc/nsswitch.conf and add the winbind package: * edit /etc/nsswitch.conf {{{ sudo gedit /etc/nsswitch.conf }}} change the line from {{{ hosts: files dns }}} to {{{ hosts: files wins dns }}} * next install winbind {{{ sudo aptitude install winbind }}} Now you should be able to mount the directory. '''''Note:''' If you experience slow dns resolution after making these changes, you can change the order of the entries to the following and you may see an improvement.'' {{{ hosts: files dns wins }}} == Server is down, filesystem is hung == If the client somehow loses contact with the Samba server, then the filesystem will probably get hung. Basically, it becomes a blackhole, eating things that try to read to/write from it (e.g. {{{ls}}}) and refusing to go away (e.g., {{{umount}}} says that the "device is busy"). Sometimes, all you need to do is restart the Samba daemon on the server machine. {{{ sudo /etc/init.d/samba restart }}} If that doesn't work, or for some reason you can't do anything on the server side, then try {{{ sudo umount -lf /mount/point }}} The {{{-f}}} option forces (possibly unclean) unmounting, and the {{{-l}}} option is for "lazy unmounting", and seems to work around "device is busy" errors that occur with just {{{-f}}}. == CIFS remote ownership enforcement == When you connect using CIFS to a server which supports Unix permissions (e.g. Samba), CIFS will by default try to enforce remote Unix ownership UIDs and Unix permissions when you try to access the share. i.e. if a file is owned by UID 502 on the remote server, then the local kernel will try to enforce the same permissions if it were owned by UID 502 on the local machine. Note: This has nothing to do with the remote server's security settings. This is an extra local ownership enforcement by the filesystem driver. It is a feature to allow use of remote share as a local drive with full Unix permissions enforcement if users match. But if this is a public share, then chances are, the remote UIDs will not make sense locally. A remote UID might be a completely different user or might not exist at all on the local machine. If remote UIDs and local UIDs do not match, then local users will have trouble using the share. To disable this, use the "noperm" mount option. Remote permissions and UIDs will still be visible, but they will not be enforced locally. == System Hangs on Shutdown == Sometimes during shutdown, networking will be turned off before the network share is unmounted. This will cause the computer to display the below code for a few minuets before shutting down (the numbers seem to change after each boot). {{{ CIFS VFS: server not responding CIFS VFS: no response for cmd ## mid ### }}} To fix this problem, and allow the computer to shut down smoothly, just change when the network share is unmounted by the file system. This can be done by running the following commands: {{{ sudo update-rc.d -f umountnfs.sh remove sudo update-rc.d umountnfs.sh stop 15 0 6 . }}} A better solution for those using Gnome: http://ubuntuforums.org/showthread.php?t=1347340 == Login without Credentials == If you want to mount the share without the credentials file you can use the entry below. I believe that by adding the '''_netdev''' in the entry below, it will not mount the share if you are not connected to the same network that the share is on or if you are not connected to a network at all. # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> //<server>/<share> <mount point> cifs rw,_netdev,user=<username>,password=<password>,uid=<uid>,gid=<gid> 0 0 Here is an example of the last line //gurnee/projects /home/jcrow/GurneeServer cifs rw,_netdev,user=DOMAIN/user,password=password,uid=1000,gid=100 0 0 The server being connected to is Gurnee, the shared folder is projects, the mount point is /home/jcrow/GurneeServer == Connect when network available == The '''_netdev''' option is also used for systems that only have networking started at user login (as when using the Gnome Network Manager package). For having network connections enabled at boot up (without requiring a user login) then tools that write to the /etc/network/interfaces file may have to be used. It is probably good policy to always use '''_netdev''' for all automatic network mounts. |
== CIFS Options Deprecated == 20 Feb 2008 TW Using dmask or fmask in the fstab file produces the following warnings: WARNING: CIFS mount option 'dmask' is deprecated. Use 'dir_mode' instead. WARNING: CIFS mount option 'fmask' is deprecated. Use 'file_mode' instead. Instead use this format: file_mode=0777,dir_mode=0777 . Or in some cases you might need to use file_mode=0777,dir_mode=0777,nounix ([[http://superuser.com/a/410561|see discussion]]) |
| Line 243: | Line 199: |
== Use of tilde in pathnames such as "credentials=~/.smbcredentials" == 20 Feb 2008 TW Curiously, using credentials=~/.smbcredentials in fstab didn't work. I had to use the full path, i.e. /home/username/.smbcredentials (This is likely because the tilde "~" is only a shell short-hand alias for "$HOME"; it isn't something recognized system-wide by all programs, especially not in a system file table where the concept of "HOME" doesn't really exist. -Ian!) ---- CategoryDocumentation |
This document describes how to mount CIFS shares permanently. The shares might be hosted on a Windows computer/server, or on a Linux/UNIX server running Samba. This document also applies to SMBFS shares, which are similar to CIFS but are deprecated and should be avoided if possible (link).
(This document does not describe how to host the shares yourself, only how to access shares that are hosted somewhere else. For hosting shares, use Samba.)
Prerequisites
We're assuming that:
- Network connections have been configured properly.
Your local (Ubuntu) username is ubuntuusername.
Share username on Windows computer is msusername.
Share password on Windows computer is mspassword.
The Windows computer's name is servername (this can be either an IP address or an assigned name).
The name of the share is sharename.
You want to mount the share in /media/windowsshare.
CIFS installation
sudo apt-get install cifs-utils
On older systems:
sudo apt-get install smbfs
Mounting unprotected (guest) network folders
First, let's create the mount directory. You will need a separate directory for each mount.
sudo mkdir /media/windowsshare
Then edit your /etc/fstab file (with root privileges) to add this line:
//servername/sharename /media/windowsshare cifs guest,uid=1000,iocharset=utf8 0 0
Where
guest indicates you don't need a password to access the share,
uid=1000 makes the Linux user specified by the id the owner of the mounted share, allowing them to rename files,
iocharset=utf8 allows access to files with names in non-English languages. This doesn't work with shares of devices like the Buffalo Tera Station, or Windows machines that export their shares using ISO8895-15.
If there is any space in the server path, you need to replace it by \040, for example //servername/My\040Documents
After you add the entry to /etc/fstab type:
sudo mount -a
This will (re)mount all entries listed in /etc/fstab.
Mount password protected network folders
The quickest way to auto-mounting a password-protected share is to edit /etc/fstab (with root privileges), to add this line:
//servername/sharename /media/windowsshare cifs username=msusername,password=mspassword,iocharset=utf8,sec=ntlm 0 0
This is not a good idea however: /etc/fstab is readable by everyone and so is your Windows password in it. The way around this is to use a credentials file. This is a file that contains just the username and password.
Using a text editor, create a file for your remote servers logon credential:
gedit ~/.smbcredentials
Enter your Windows username and password in the file:
username=msusername password=mspassword
Save the file, exit the editor.
Change the permissions of the file to prevent unwanted access to your credentials:
chmod 600 ~/.smbcredentials
Then edit your /etc/fstab file (with root privileges) to add this line (replacing the insecure line in the example above, if you added it):
//servername/sharename /media/windowsshare cifs credentials=/home/ubuntuusername/.smbcredentials,iocharset=utf8,sec=ntlm 0 0
Save the file, exit the editor.
Finally, test the fstab entry by issuing:
sudo mount -a
If there are no errors, you should test how it works after a reboot. Your remote share should mount automatically.
Special permissions
If you need special permission (like chmod etc.), you'll need to add a uid (short for 'user id') or gid (for 'group id') parameter to the share's mount options.
//servername/sharename /media/windowsshare cifs uid=ubuntuuser,credentials=/home/ubuntuuser/.smbcredentials,iocharset=utf8,sec=ntlm 0 0
Mount password protected shares using libpam_mount (Ubuntu 9.04)
In addition to the initial assumptions, we're assuming that
Your username and password are the same on the Ubuntu machine and on the network drive.
Install libpam-mount:
sudo apt-get install libpam-mount
Edit /etc/security/pam_mount.conf.xml using your preferred text editor.
gksudo gedit /etc/security/pam_mount.conf.xml
First, we're moving the user specific config bits to a file which users can actually edit themselves: remove the commenting tags (<!-- and -->) surrounding the section called <luserconf name=".pam_mount.conf.xml" />. Save the file when done. With this in place, users can create their own ~/.pam_mount.conf.xml.
gedit ~/.pam_mount.conf.xml
Add the following:
<?xml version="1.0" encoding="utf-8" ?> <pam_mount> <volume options="uid=%(USER),gid=100,dmask=0700" user="*" mountpoint="/media/windowsshare" path="sharename" server="servername" fstype="cifs" /> </pam_mount>
Troubleshooting
Login errors
If you get the error "mount error(13) permission denied", then the server denied your access. Here are the first things to check:
- Are you using a valid username and password? Does that account really have access to this folder?
Do you have whitespace in your credentials file? It should be password=mspassword, not password = mspassword.
Do you need a domain? For example, if you are told that your username is SALES\sally, then actually your username is sally and your domain is SALES. The fstab entry should read: ...username=sally,password=pass,domain=SALES,... Or: ...credentials=/path/to/file,domain=SALES,...
Is the security setting correct? The most common is sec=ntlm, but you can also try the other options listed at the mount.cifs man page. The man page list leaves out the option sec=lanman for some reason, but you should try that one as well (see discussion).
Unprotected network folder won't automount
I've had a situation where an unprotected network folder wouldn't automount during bootup, but after manually entering "sudo mount -a" was mounted correctly. I solved this by replacing the "guest" option by "username=guest,password=". If anyone has an explanation for this, please leave a comment.
//servername/sharename /media/windowsshare smbfs username=guest,password=,uid=1000,iocharset=utf8,codepage=unicode,unicode 0 0
Mount during login instead of boot
If for some reason/etc/rc0.d/S31umountnfs.sh (networking problems for example) the automatic mounting during boot doesn't work, you can add the "noauto" parameter to your smbfs fstab entry and then have the share mounted at login.
In /etc/fstab:
//servername/sharename /media/windowsshare cifs noauto,credentials=/home/ubuntuusername/.smbpasswd 0 0
In /etc/rc.local:
mount /media/windowsshare exit 0
Slow shutdown due to a CIFS/Network Manager bug
If you use Network Manager, and are getting really slow shutdowns, it's probably because NM shuts down before unmounting the network shares. That will cause CIFS to hang and wait for 60 seconds or so. Here's how to fix it:/etc/rc0.d/S31umountnfs.sh
sudo ln -s /etc/init.d/umountnfs.sh /etc/rc0.d/K14umountnfs.sh sudo ln -s /etc/init.d/umountnfs.sh /etc/rc6.d/K14umountnfs.sh
Ubuntu 12.04 already runs umountnfs.sh at reboot and shutdown by default (/etc/rc0.d/S31umountnfs.sh and /etc/rc6.d/S31umountnfs.sh) so this is no longer necessary.
CIFS Options Deprecated
20 Feb 2008 TW
Using dmask or fmask in the fstab file produces the following warnings: WARNING: CIFS mount option 'dmask' is deprecated. Use 'dir_mode' instead. WARNING: CIFS mount option 'fmask' is deprecated. Use 'file_mode' instead.
Instead use this format: file_mode=0777,dir_mode=0777 . Or in some cases you might need to use file_mode=0777,dir_mode=0777,nounix (see discussion)
Use of tilde in pathnames such as "credentials=~/.smbcredentials"
20 Feb 2008 TW
Curiously, using credentials=~/.smbcredentials in fstab didn't work. I had to use the full path, i.e. /home/username/.smbcredentials
(This is likely because the tilde "~" is only a shell short-hand alias for "$HOME"; it isn't something recognized system-wide by all programs, especially not in a system file table where the concept of "HOME" doesn't really exist. -Ian!)
MountWindowsSharesPermanently (last edited 2024-04-18 09:12:09 by sally-makin)