then edit your fstab to ensure your Samba shares are mounted at startup and become visible inside your local file system (The standard to do that is inside /mnt or /media)
If you would run into specific issues trying that, please leave another message.
Looking at the information already provided, this would do what you want:
# Create NAS mountpoint
sudo mkdir /mnt/NAS
mount -t cifs //192.168.50.112/home /mnt/NAS -o username=james,password=JamesPassword,domain=WORKGROUP`
Where obviously james is the samba share’s username and JamesPassword, is that username’s password and WORKGROUP is the actual workgroup name
If that works, add the following line as the last line on your fstab:
So I got the temporary way to work, but on startup the fstab didn’t work, I had to use a terminal based emergency mode, and I ended up just using vim to remove the line I added. Instead of using /mnt/NAS I’m using /home/james/home, what does “cifs uid=1000” do, I think that’s what it didn’t work but the temporary way to mount it did.
So I tried it again, and this time after restarting, I got to my desktop, but it didn’t mount, when I access the folder, in dolphin, it says An error occurred while accessing ‘/home/james/home’, the system responded: mount: /etc/fstab: parse error at line 12 – ignored mount: /home/james/home: can’t find in /etc/fstab.
This is what I have in fstab for it //192.168.50.112/home /home/james/home cifs uid=1001, username=MY_USERNAME,password=MY_PASSWORD,domain=WORKGROUP
kio-fuse package will automatically create a virtual directory on our machine after you manually mount your smb:// folder with dolphin.
So it will be accessible to all applications by /run/user/1001/kio-fuse-xxx/smb/ while with fstab you have /home/james/home/
So it’s another solution (without fstab/mount at boot) but:
Okay, so that works out of the box, and I like that, but I would rather get fstab to work better, it would automatically do it now that I vaguely understand how it works. With this kio method, I can navigate, to the folder, but I have to do a lot of clunky searching for the path, currently I found part of the solution was to get rid of a space but now I’m not getting write permission all the way so idk whether to settle for this or not.
So i’ve found part of the problem, initially, was that I had a space during the options, and apparently, that’s not allowed. Anyways, I’ve got it kinda configured right, almost verbatim what you’ve been typing with all variations, and they all return this error. “mount.cifs: permission denied”, weirdest thing, If I run mount -a, I get that error, if I run sudo mount -a, no problem.
and also provide the full mount command you’re using (not the mount --all command but the full mount command you used from here before you added it to the fstab file…)
P.S. also provide the same output from the computer that is running the Samba share when logged in there…
P.P.S.
Okay, but the whole issue seems to be that only root / sudo can do it, so even if I run sudo, I’m going to get the same issue with fstab since that’s the same logic?