Ok, so the authentication works, but whatever you supplied for the share doesn’t exists or not allowed. Only you can know what shares are actually available for a given user…
smbclient -L //xxx.xxx.xx.xx -U user -m SMB3 -d 3
The share I’m trying to access is displayed, I can mount it with Dolphin indeed.
This is too difficult/tedious for me to diagnose remotely. This is why showing the exact command typed (as preformatted text) is important. Do make sure you’re trying to mount the top-level share, not a subfolder directly when using smbclient.
You should be able to use smbclient to access the share the same way Dolphin does. If you believe there is a bug, you’ll need to raise a bug report, although so far I’m not convinced there is one.
Thanks for being very patient, I don’t want to expose on the forum my net structure so I thank you again for your effort.
You were right, I was trying to mount a subfolder with smbclient (while with mount -t cifs I was using the option ‘subdir=’).
This is now the output without the subdir:
~> smbclient -L //xxx.xxx.xx.xx/Folder1 -U user -m SMB3 -d 3
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[global]"
added interface wlp0s20f3 ip= xxx.xxx.xx.xx bcast= netmask=ffff:ffff:ffff:ffff::
added interface wlp0s20f3 ip=2 xxx.xxx.xx.xx bcast= netmask=ffff:ffff:ffff:ffff::
added interface ipv6leakintrf0 ip=f xxx.xxx.xx.xx bcast= netmask=ffff:ffff:ffff:ffff::
added interface wlp0s20f3 ip= xxx.xxx.xx.xx bcast= xxx.xxx.xx.xx netmask=255.255.255.0
Client started (version 4.23.5-git.463.513487e87f1SUSE-oS16.9-x86_64).
Connecting to xxx.xxx.xx.xx at port 445
Connecting to xxx.xxx.xx.xx at port 139
GENSEC backend 'gssapi_spnego' registered
GENSEC backend 'gssapi_krb5' registered
GENSEC backend 'gssapi_krb5_sasl' registered
GENSEC backend 'spnego' registered
GENSEC backend 'schannel' registered
GENSEC backend 'ncalrpc_as_system' registered
GENSEC backend 'sasl-EXTERNAL' registered
GENSEC backend 'ntlmssp' registered
GENSEC backend 'ntlmssp_resume_ccache' registered
GENSEC backend 'http_basic' registered
GENSEC backend 'http_ntlm' registered
GENSEC backend 'http_negotiate' registered
GENSEC backend 'krb5' registered
GENSEC backend 'fake_gssapi_krb5' registered
gensec_gse_client_start: Not using kerberos to cifs/ xxx.xxx.xx.xx as WORKGROUP\user: NT_STATUS_INVALID_PARAMETER
Got challenge flags:
Got NTLMSSP neg_flags=0x628a8215
Password for [WORKGROUP\user]:
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x62088215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x62088215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x62088215
Sharename Type Comment
--------- ---- -------
xxxxxxxx Disk
xxxxxx Disk
xxxxxx Disk homes contains all users' home
xxxxxx Disk System default shared folder
xxxxxx Disk System default shared folder
Folder1 Disk
xxxxxx Disk System default shared folder
xxxxxx IPC IPC Service ()
xxxxxx Disk Home directory of user
SMB1 disabled -- no workgroup available
Thanks for the update. This shows that the credentials and authentication are fine. The earlier failures happened because you tried to mount a subfolder directly using the unsupported subdir= option. You should mount the share root Folder1 first. After that, all subdirectories can be accessed normally.
You are right, removing the subdir made mount -t cifs work again, and SMB4k works too without including the subdir. Will I be able to mount the subdir only again ?
You cannot mount a sub-directory directly with mount.cifs. CIFS only allows mounting the share root. You can access any subfolders after mounting the share. The same limitation applies to SMB4K. It will also need the share root to be mounted first.
The strange this is that I was able to do so before the smb4k update. What changed ?
IIRC, older versions of CIFS allowed mounting of sub-directories if SMBv1 was enabled, but modern CIFS with SMB2 or SMB3 does not support this.
Thank you so much for being so kind, patient and detailed with your answers.
1 Like
Glad to have been of guidance. FWIW, I did see a workaround described involving the use of a bind mount. Like this…
# Mount the share root
sudo mount -t cifs //server/Folder1 /mnt/Folder1 -o username=user,vers=3.0
# Bind the subdirectory to another path
sudo mount --bind /mnt/Folder1/subfolder /mnt/SubfolderMount
That approach can’t be used for SMB4K though.
A post was split to a new topic: Webmin system administration tool