You are not logged in.

#1 2021-12-26 20:07:43

Vizitor
Member
Registered: 2015-01-05
Posts: 81

[SOLVED] Caja can't connect to NAS after setting password on it

Hi,
I am using Mate DE. Connecting Caja to Network Attached Storage is working OK, when entering

smb://192.168.1.4/Volume_1

into caja location field.

But, today I decided to setup password on that NAS. And Caja popups login window with credentials (username/workgroup/password) (forget pw immediately/ remember pw for this session/ remember pw forever)
I filled in requested infos, but login window just popups again asking same thing again, then I entered credentials again, window popups again...
and so on. I don't have samba installed, only /etc/samba/smb.conf with

[global]
workgroup = mygroup
client min protocol = NT1

because it is an old NAS that only supports NT1 protocol, and this is the only way to get access to it.

also

sudo mount -t cifs //192.168.1.5/Volume_1 /mnt/nas2 -o user=<NAME>,password=<PASSWORD>,sec=ntlm,vers=1.0

does not working anymore because someone decided so, as I readed few months ago somewhere on this forum.

NTLM support removed

I tryed some live distro (MX KDE) and Dolphin file manager can access NAS files after entering user/password without problems. (of course, with adding client min protocol = NT1 to smb.conf)

Last edited by Vizitor (2022-01-23 20:14:40)

Offline

#2 2021-12-26 20:58:18

seth
Member
Registered: 2012-09-03
Posts: 49,978

Re: [SOLVED] Caja can't connect to NAS after setting password on it

Dolphin and caja don't use the same smb protocol implementation to begin with (kio ./. gvfs), so that test is useless - there's a good chance that dolphin works on the installed system as well.
You could test it against eg. nautilus. It that shows the same problem, it's likely because of gvfsd-smb, try to debug gfvs: https://wiki.gnome.org/Projects/gvfs/debugging

Online

#3 2021-12-26 21:28:58

Vizitor
Member
Registered: 2015-01-05
Posts: 81

Re: [SOLVED] Caja can't connect to NAS after setting password on it

I installed nautilus and it has same error.
I'll try to debug. TY

Offline

#4 2021-12-26 21:48:12

Vizitor
Member
Registered: 2015-01-05
Posts: 81

Re: [SOLVED] Caja can't connect to NAS after setting password on it

Here is debug log:

$ GVFS_DEBUG=1 $(find /usr/lib* -name gvfsd 2>/dev/null) --replace 2>&1 | tee gvfsd.log
smb-network: g_vfs_backend_smb_browse_init: default workgroup = 'NULL'
smb-network: Added new job source 0x557064123080 (GVfsBackendSmbBrowse)
smb-network: Queued new job 0x557064128970 (GVfsJobMount)
smb-network: do_mount - URI = smb://192.168.1.4
smb-network: do_mount - try #0 
smb-network: looking up cached server '192.168.1.4'\'IPC$', user 'SS';'v'
smb-network:   returning (nil)
smb-network: auth_callback - anonymous pass
smb-network: auth_callback - out: last_user = 'v', last_domain = 'SS'
smb-network: looking up cached server '192.168.1.4'\'IPC$', user 'SS';'v'
smb-network:   returning (nil)
smb-network: looking up cached server '192.168.1.4'\'IPC$', user 'SS';'v'
smb-network:   returning (nil)
smb-network: auth_callback - anonymous pass
smb-network: auth_callback - out: last_user = 'v', last_domain = 'SS'
smb-network: looking up cached server '192.168.1.4'\'IPC$', user 'SS';'v'
smb-network:   returning (nil)
Kerberos auth with 'v@SS' (SS\v) to access '192.168.1.4' not possible
smb-network: adding cached server '192.168.1.4'\'IPC$', user 'SS';'v' with data 0x7f3b54050d60
smb-network: do_mount - [smb://192.168.1.4; 0] dir = 0x7f3b5401bd40, cancelled = 0, errno = [2] 'No such file or directory' 
smb-network: update_cache - updating...
smb-network: update_cache - done.
smb-network: do_mount - login successful, res = 1
smb-network: send_reply(0x557064128970), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=971)
smb-network: Queued new job 0x55706410e210 (GVfsJobQueryInfo)
smb-network: send_reply(0x55706410e210), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=5736)
smb-network: Queued new job 0x55706410e350 (GVfsJobQueryInfo)
smb-network: send_reply(0x55706410e350), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:CreateDirectoryMonitor (pid=5736)
smb-network: Queued new job 0x7f3b54019d60 (GVfsJobCreateMonitor)
smb-network: send_reply(0x7f3b54019d60), failed=1 (Operation not supported)
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo (pid=5736)
smb-network: Queued new job 0x7f3b54019df0 (GVfsJobQueryFsInfo)
smb-network: send_reply(0x7f3b54019df0), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo (pid=5736)
smb-network: Queued new job 0x7f3b54019e80 (GVfsJobQueryFsInfo)
smb-network: send_reply(0x7f3b54019e80), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5736)
smb-network: Queued new job 0x5570641211a0 (GVfsJobEnumerate)
smb-network: send_reply(0x5570641211a0), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=5736)
smb-network: Queued new job 0x55706410e490 (GVfsJobQueryInfo)
smb-network: send_reply(0x55706410e490), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=5736)
smb-network: Queued new job 0x55706410e530 (GVfsJobQueryInfo)
smb-network: send_reply(0x55706410e530), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=5736)
smb-network: Queued new job 0x55706410e5d0 (GVfsJobQueryInfo)
smb-network: send_reply(0x55706410e5d0), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo (pid=5736)
smb-network: Queued new job 0x557064151020 (GVfsJobQueryFsInfo)
smb-network: send_reply(0x557064151020), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=5736)
smb-network: Queued new job 0x55706410e5d0 (GVfsJobQueryInfo)
smb-network: send_reply(0x55706410e5d0), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=5736)
smb-network: Queued new job 0x55706410e530 (GVfsJobQueryInfo)
smb-network: send_reply(0x55706410e530), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo (pid=5736)
smb-network: Queued new job 0x5570641510b0 (GVfsJobQueryFsInfo)
smb-network: send_reply(0x5570641510b0), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=5736)
smb-network: Queued new job 0x55706410e490 (GVfsJobQueryInfo)
smb-network: send_reply(0x55706410e490), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:MountMountable (pid=5736)
smb-network: Queued new job 0x55706410e030 (GVfsJobMountMountable)
smb-network: send_reply(0x55706410e030), failed=0 ()
smb: g_vfs_backend_smb_init: default workgroup = 'NULL'
smb: Added new job source 0x558c9574e080 (GVfsBackendSmb)
smb: Queued new job 0x558c9574f160 (GVfsJobMount)
smb: do_mount - URI = smb://192.168.1.4/volume_1
smb: do_mount - try #0 
smb: auth_callback - kerberos pass
smb: auth_callback - out: last_user = 'v', last_domain = 'SS'
Kerberos auth with 'v@SS' (SS\v) to access '192.168.1.4' not possible
smb: do_mount - [smb://192.168.1.4/volume_1; 0] res = -1, cancelled = 0, errno = [1] 'Operation not permitted' 
smb: do_mount - enabling NTLMSSP fallback
smb: do_mount - try #1 
smb: auth_callback - ccache pass
smb: auth_callback - out: last_user = 'v', last_domain = 'SS'
smb: do_mount - [smb://192.168.1.4/volume_1; 1] res = -1, cancelled = 0, errno = [1] 'Operation not permitted' 
smb: do_mount - try #2 
smb: auth_callback - normal pass
smb: auth_callback - asking for password...
smb: auth_callback - out: last_user = 'v', last_domain = 'SS'
smb_signing_good: BAD SIG: seq 1
smb: do_mount - [smb://192.168.1.4/volume_1; 2] res = -1, cancelled = 0, errno = [1] 'Operation not permitted' 
smb: do_mount - try #3 
smb: auth_callback - normal pass
smb: auth_callback - asking for password...
smb: auth_callback - out: last_user = 'v', last_domain = 'SS'
smb: do_mount - [smb://192.168.1.4/volume_1; 3] res = -1, cancelled = 0, errno = [1] 'Operation not permitted' 
smb: do_mount - try #4 
smb: auth_callback - anonymous login pass
smb: auth_callback - out: last_user = 'v', last_domain = 'SS'
smb: do_mount - [smb://192.168.1.4/volume_1; 4] res = -1, cancelled = 0, errno = [13] 'Permission denied' 
smb: do_mount - try #5 
smb: auth_callback - normal pass
smb: auth_callback - asking for password...
smb: auth_callback - out: last_user = 'v', last_domain = 'SS'
smb: do_mount - [smb://192.168.1.4/volume_1; 5] res = -1, cancelled = 0, errno = [1] 'Operation not permitted' 
smb: do_mount - try #6 
smb: auth_callback - anonymous login pass
smb: auth_callback - out: last_user = 'v', last_domain = 'SS'
smb: do_mount - [smb://192.168.1.4/volume_1; 6] res = -1, cancelled = 0, errno = [13] 'Permission denied' 
smb: do_mount - try #7 
smb: auth_callback - normal pass
smb: auth_callback - asking for password...
smb: auth_callback - out: last_user = 'ABORT', last_domain = 'SS'
smb: do_mount - [smb://192.168.1.4/volume_1; 7] res = -1, cancelled = 1, errno = [1] 'Operation not permitted' 
smb: do_mount - (errno != EPERM && errno != EACCES), cancelled = 1, breaking
smb: send_reply(0x558c9574f160), failed=1 (Password dialog cancelled)
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo (pid=5736)
smb-network: Queued new job 0x557064151140 (GVfsJobQueryFsInfo)
smb-network: send_reply(0x557064151140), failed=0 ()
smb: g_vfs_backend_smb_init: default workgroup = 'NULL'
smb: Added new job source 0x55ac3346e080 (GVfsBackendSmb)
smb: Queued new job 0x55ac3346f960 (GVfsJobMount)
smb: do_mount - URI = smb://192.168.1.4/volume_1
smb: do_mount - try #0 
smb: auth_callback - kerberos pass
smb: auth_callback - out: last_user = 'v', last_domain = 'SS'
Kerberos auth with 'v@SS' (SS\v) to access '192.168.1.4' not possible
smb: do_mount - [smb://192.168.1.4/volume_1; 0] res = -1, cancelled = 0, errno = [1] 'Operation not permitted' 
smb: do_mount - enabling NTLMSSP fallback
smb: do_mount - try #1 
smb: auth_callback - ccache pass
smb: auth_callback - out: last_user = 'v', last_domain = 'SS'
smb: do_mount - [smb://192.168.1.4/volume_1; 1] res = -1, cancelled = 0, errno = [1] 'Operation not permitted' 
smb: do_mount - try #2 
smb: auth_callback - normal pass
smb: auth_callback - asking for password...
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=5736)
smb-network: Queued new job 0x55706410e3f0 (GVfsJobQueryInfo)
smb-network: update_cache - updating...
smb-network: looking up cached server '192.168.1.4'\'IPC$', user 'SS';'v'
smb-network:   returning 0x7f3b54050d60
smb-network: update_cache - done.
smb-network: send_reply(0x55706410e3f0), failed=0 ()
smb: auth_callback - out: last_user = 'ABORT', last_domain = 'SS'
smb: do_mount - [smb://192.168.1.4/volume_1; 2] res = -1, cancelled = 1, errno = [1] 'Operation not permitted' 
smb: do_mount - (errno != EPERM && errno != EACCES), cancelled = 1, breaking
smb: send_reply(0x55ac3346f960), failed=1 (Password dialog cancelled)
^C

... but I don't have idea what next.

Offline

#5 2021-12-26 23:12:44

seth
Member
Registered: 2012-09-03
Posts: 49,978

Re: [SOLVED] Caja can't connect to NAS after setting password on it

It tries to use kerberos, fails because that's not supported by the server,  tries ntlmssp, fails for probably the same reason (that's ntlmv2)
I'd tell you to try to deny ntlmv2, but https://bugs.launchpad.net/ubuntu/+sour … ug/1917364 suggests that this will just lead to a different manifestation of the same gfvs-smb bug.

Does the NAS do NFS?

Edit: my keyboard had a stroke…

Last edited by seth (2021-12-26 23:13:20)

Online

#6 2021-12-27 00:00:44

Vizitor
Member
Registered: 2015-01-05
Posts: 81

Re: [SOLVED] Caja can't connect to NAS after setting password on it

NAS does not have NFS, only FTP;
so options are
1) Install KDE/Plasma   2) Try FTP   3) Disable password access on NAS
OK, tryied FTP from caja, it works (crappy, but ...).
Installed Plasma, Dolphin behave like caja  ... sad

So, I guess, this gvfs-circus will never end.

Last edited by Vizitor (2021-12-27 00:57:52)

Offline

#7 2021-12-27 07:56:10

seth
Member
Registered: 2012-09-03
Posts: 49,978

Re: [SOLVED] Caja can't connect to NAS after setting password on it

Idt how their implementations work internally, but they might be affected by the same NTLM withdrawal.

This product's last date of support is on: 08/11/2013

eeewww…

Buu-uuht:
https://media.dlink.eu/support/products … 042011.zip

Software: NFS Package v1.01 1.10	Software: NFS Package v1.01	03/04/2011

And since it's an extfs drive, you can just use regular POSIX permissions (like on the local drive) to restrict access.

Online

#8 2021-12-27 13:15:26

Vizitor
Member
Registered: 2015-01-05
Posts: 81

Re: [SOLVED] Caja can't connect to NAS after setting password on it

I'll try that.
Still

seth wrote:

Dolphin and caja don't use the same smb protocol implementation to begin with (kio ./. gvfs), so that test is useless - there's a good chance that dolphin works on the installed system as well.

I wonder why installed KDE (Dolphin) can't open as tested live  'MX KDE Linux' can?
Is it because I still have installed Mate DE (with gvfs-*) ?
Would clean Arch installation with KDE work (I mean will Dolphin ..)?

Offline

#9 2021-12-27 13:16:25

seth
Member
Registered: 2012-09-03
Posts: 49,978

Re: [SOLVED] Caja can't connect to NAS after setting password on it

What kernel version does 'MX KDE Linux' run?

Online

#10 2021-12-27 13:54:21

Vizitor
Member
Registered: 2015-01-05
Posts: 81

Re: [SOLVED] Caja can't connect to NAS after setting password on it

seth wrote:

What kernel version does 'MX KDE Linux' run?

5.10

Last edited by Vizitor (2021-12-27 13:55:00)

Offline

#11 2021-12-27 13:56:25

seth
Member
Registered: 2012-09-03
Posts: 49,978

Re: [SOLVED] Caja can't connect to NAS after setting password on it

Does it work on arch w/ the lts kernel?

Online

#12 2021-12-27 14:28:06

Vizitor
Member
Registered: 2015-01-05
Posts: 81

Re: [SOLVED] Caja can't connect to NAS after setting password on it

I'll try it now, in the meantime:
( Playing with NFS:  )

$ showmount 192.168.1.4 -e
Export list for 192.168.1.4:
/mnt/HD_a2 NAS1
$ rpcinfo -p 192.168.1.4
   program vers proto   port  service
    100000    2   tcp    111  portmapper
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100021    1   udp   1044  nlockmgr
    100021    3   udp   1044  nlockmgr
    100021    4   udp   1044  nlockmgr
    100021    1   tcp   1026  nlockmgr
    100021    3   tcp   1026  nlockmgr
    100021    4   tcp   1026  nlockmgr
    100005    1   udp    922  mountd
    100005    1   tcp    925  mountd
    100005    2   udp    922  mountd
    100005    2   tcp    925  mountd
    100005    3   udp    922  mountd
    100005    3   tcp    925  mountd
$ sudo mount -t nfs 192.168.1.4:/mnt/HD_a2 /mnt/nas
Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service.
mount.nfs: Protocol not supported
sudo mount -t nfs 192.168.1.4:/mnt/HD_a2 /mnt/nas
mount.nfs: Protocol not supported 
sudo mount /mnt/nas -v
mount.nfs: timeout set for Mon Dec 27 15:50:25 2021
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.4,clientaddr=192.168.1.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.1.4,clientaddr=192.168.1.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,addr=192.168.1.4,clientaddr=192.168.1.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.1.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.4 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.4 prog 100005 vers 3 prot UDP port 922
mount.nfs: mount(2): Permission denied
mount.nfs: Protocol not supported 

from fstab:

192.168.1.4:/HD_a2/mnt  /mnt/nas nfs defaults,_netdev 0 0

from journalctl -b :

Dec 27 16:15:16 bprime systemd[1]: Finished Network Manager Wait Online.
Dec 27 16:15:16 bprime systemd[1]: Reached target Network is Online.
Dec 27 16:15:16 bprime systemd[1]: Mounting /mnt/nas...
Dec 27 16:15:16 bprime kernel: FS-Cache: Loaded
Dec 27 16:15:16 bprime kernel: RPC: Registered named UNIX socket transport module.
Dec 27 16:15:16 bprime kernel: RPC: Registered udp transport module.
Dec 27 16:15:16 bprime kernel: RPC: Registered tcp transport module.
Dec 27 16:15:16 bprime kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Dec 27 16:15:17 bprime kernel: FS-Cache: Netfs 'nfs' registered for caching
Dec 27 16:15:17 bprime kernel: Key type dns_resolver registered
Dec 27 16:15:17 bprime kernel: NFS: Registering the id_resolver key type
Dec 27 16:15:17 bprime kernel: Key type id_resolver registered
Dec 27 16:15:17 bprime kernel: Key type id_legacy registered
Dec 27 16:15:17 bprime mount[833]: mount.nfs: Network is unreachable
Dec 27 16:15:17 bprime systemd[1]: mnt-nas.mount: Mount process exited, code=exited, status=32/n/a
Dec 27 16:15:17 bprime systemd[1]: mnt-nas.mount: Failed with result 'exit-code'.
Dec 27 16:15:17 bprime systemd[1]: Failed to mount /mnt/nas.
Dec 27 16:15:17 bprime systemd[1]: Dependency failed for Remote File Systems.
Dec 27 16:15:17 bprime systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'.
Dec 27 16:15:17 bprime systemd[1]: Starting Permit User Sessions...
Dec 27 16:15:17 bprime systemd[1]: Finished Permit User Sessions.
Dec 27 16:15:17 bprime systemd[1]: Reached target Multi-User System.
Dec 27 16:15:17 bprime systemd[1]: Started Simple Desktop Display Manager.
Dec 27 16:15:17 bprime systemd[1]: Reached target Graphical Interface.
Dec 27 16:15:17 bprime systemd[1]: Startup finished in 17.641s (firmware) + 64ms (loader) + 1min 33.392s (kernel) + 6.747s (userspace) = 1min 57.846s.
Dec 27 16:15:17 bprime sddm[842]: Initializing...
Dec 27 16:15:17 bprime sddm[842]: Starting...
Dec 27 16:15:17 bprime sddm[842]: Logind interface found
Dec 27 16:15:17 bprime sddm[842]: Adding new display on vt 1 ...
Dec 27 16:15:17 bprime sddm[842]: Loading theme configuration from ""
Dec 27 16:15:17 bprime sddm[842]: Display server starting...
Dec 27 16:15:17 bprime sddm[842]: Adding cookie to "/var/run/sddm/{be8cb72b-0c91-48ae-b4f2-f3cf62fdb5fa}"
Dec 27 16:15:17 bprime sddm[842]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{be8cb72b-0c91-48ae-b4f2-f3cf62fdb5fa} -noreset -displayfd 17
Dec 27 16:15:18 bprime NetworkManager[773]: <info>  [1640618118.8905] dhcp4 (net0): state changed unknown -> bound, address=192.168.1.2
Dec 27 16:15:18 bprime NetworkManager[773]: <info>  [1640618118.8915] manager: NetworkManager state is now CONNECTED_SITE
Dec 27 16:15:18 bprime NetworkManager[773]: <info>  [1640618118.8916] policy: set 'Wired connection 1' (net0) as default for IPv4 routing and DNS

Offline

#13 2021-12-27 14:55:16

seth
Member
Registered: 2012-09-03
Posts: 49,978

Re: [SOLVED] Caja can't connect to NAS after setting password on it

I'll blindly assume that "NAS1" is neither the client you're trying to access this from not an alias for a network segment?
Try configure the exportfs for 192.168.1.0/24 instead (on the NAS)

Online

#14 2021-12-27 15:07:28

Vizitor
Member
Registered: 2015-01-05
Posts: 81

Re: [SOLVED] Caja can't connect to NAS after setting password on it

Downgraded to kernel 5.10, system standing at "Reached target Graphical interface" and not geting on GUI.
Updated back to 5.15
'NAS1' is the name of, well NAS, it has addr 192.168.1.4
I'll try more

Offline

#15 2022-01-23 20:13:59

Vizitor
Member
Registered: 2015-01-05
Posts: 81

Re: [SOLVED] Caja can't connect to NAS after setting password on it

Solved by installing ALT-F ( free and open source alternative firmware for the DLINK DNS-320/320L/321/323/325/327L and DNR-322L )
which has added SMB2 protocol, NFS, ext4 and tonz of other options :-)

So now it works:

 ~ $ showmount -e 192.168.1.4
Export list for 192.168.1.4:
/mnt/sda2 * 
~ $ sudo mount -t nfs 192.168.1.4:/mnt/sda2 /mnt 

and it is successfuly mounted! :-)

Also smb mount (with password accepting pop-up window) from Nemo file manager works.

Out of topic:
Notice I said "Nemo" and not "Caja", because recently, something between Mate DE and nVidia and god knows what is terribly wrong, so I replaced Mate DE with Cinnamon DE.

Offline

Board footer

Powered by FluxBB