I don't know what makes dolphin choke - the referenced topic - is also a dolphin user - and a samba share - albeit a NAS not a Manjaro computer. Any help or tips would be much appreciated! No error, no verbose, just empty nothing. So, something seems to be off with the name resolution? To check it out, I wanted to look a the smb tree by using the command: smbtree First I mounted not by using the nameshare, but the IP: "domain=WORKGROUP,username=sampleuser,password=*****,file_mode=0755,dir_mode=0755,noperm" //192.168.0.101/home /mnt/home
CIFS VFS: cifs_mount failed w/return code = -2
To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. More specifically, dmesg logs the error as following: CIFS: Attempting to mount //SERVER/home
The mounting always worked, but today I updated both machines and after that, the above command threw the following error: mount error(2): No such file or directory Passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully* Usershare path = /var/lib/samba/usershare Name resolve order = lmhosts bcast host wins This is the corresponding smb.conf, which is similar on both machines: For this, I use the following command sudo mount -t cifs -o "domain=WORKGROUP,username=sampleuser,password=*****,file_mode=0755,dir_mode=0755,noperm" //SERVER/home /mnt/home To be able to do so via the software FreeFileSync, I need to manually mount my SMB shares to my local file system. My case: I use FreeFileSync for backing up my data from my personal notebook, to my stationary PC (here called SERVER). I encounter a strange problem, apparently since the last stable update.
0 kommentar(er)
