You use kde !
Other way to access to smb:// by local file system without fstab (use kio-fuse package):
If smb is mounted with dolphin, we can access by local directory:
/run/user/<USER-ID>/kio-fuse-***/smb/<IP-SERVER>
For test (and found directory): open smb directory in dolpin and open console by F4
Can you explain a little bit with how that works, I’m not really sure how or what this is accomplishing?
We use fstab OR dolphin-smb://
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.
in fstab you can add (for test) in options file_mode=0777,dir_mode=0777
so the final line in fstab becomes:
//192.168.50.112/home /home/james/home cifs uid=1001, username=MY_USERNAME,password=MY_PASSWORD,domain=WORKGROUP,file_mode=0777,dir_mode=0777 0 0
P.S. @papajoke Oh drat! forgot about the 0 0! Thanks for helping out!
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.
Sorry for being confusing.
Please provide the output to:
echo $USER
groups
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.
echo $User on computer:
james
groups output on computer:
sys network power sambashare lp wheel autologin james
Server user output:
jamess7995
groups:
jamess7995 adm cdrom sudo dip plugdev lxd
Mount command that you would use in terminal before configuring fstab:
mount -t cifs //192.168.50.112/home /home/james/home -o username=sora,password=123456,domain=leviathan
, which outputs ““mount: only root can use “–options” option””, using sudo resolves that and it just works at that point
Ah, you’re logging on under different user names and uids on both client and server.
Try:
mount -t cifs //192.168.50.112/home -o rw,username=sora,password=123456,domain=leviathan,vers=3.0 /home/james/home
if that doesn’t work, what is the version number of the Samba running on the server?
Also, I’d make the server and client UIDs the same and use james instead of sora , but that’s just an opinion, not a technical necessity.
Still get “mount: only root can use “–options” option”
from server:
Version 4.7.6-Ubuntu```Yeah, add sudo, sorry!!!
That should work. what’s your samba config file on the server?
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?
Nope. fstab always runs as root.
The mount command we’re testing is just to ensure we get the fstab correct before modifying it…
Okay, so just like before, the command works only with sudo, not sure why we did that but what’s next.
If
mount -t cifs //192.168.50.112/home /home/james/home -o username=sora,password=123456,domain=leviathan
worked, you should add at the end of fstab:
//192.168.50.112/home /home/james/home cifs noauto,x-systemd.automount,x-systemd.device-timeout=10,rw,username=sora,password=123456,domain=leviathan 0 0
and then type
sudo mount --all
# as a first character¹ to the line you just added and report back the exact error. /home/james/home automatically.If it does all work, that’s what the Solution button is for!!
Note 1 the # will make that line a comment, so not do anything with it any more…
so running that, does not give me write permission, where as before, I wanna emphasize, just to be sure, the commands were working, and their respective recommended fstab command were not working, unless I ran sudo mount -a
sudo mount -a is the same as sudo mount --all is the same as fstab.
So if you’re telling me:
mount --all gives you write permissions but fstab does not?Please clarify what the remaining issue is?
sorry for the long hiatus, I encountered a new read and write issue, that was entirely irrelevant but I thought I messed something up, so where I’m at, if I run an individual command, I can get it to mount the samba share, if I add a command to fstab, I have to use sudo mount -a, I can’t just use mount --a, which isn’t a big deal. the only problem is that fstab requires sudo, which means I can’t get it to happen at startup
fstab does not contain the mount command anywhere, so this:
is by design… 
fstab runs as root at startup so I don’t understand what you’re trying to say.
Here is more information on fstab
