Unable to specify smb version (dialect) in mount option

[dyle]

Hi *,

Since my last update to the Kubuntu 19.10 kernel, most of my bookmarked shared stopped working.

It seems, that there is a version conflict due to the samba version used. While trying to mount a share via smb4k the kernel log reads:

[ 2615.824909] CIFS VFS: cifs_mount failed w/return code = -2
[ 2615.847801] CIFS: Attempting to mount ...<cut on purpose>...
[ 2615.847829] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). 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.
[ 2615.866938] CIFS VFS: cifs_mount failed w/return code = -2

It seems, issuing a "vers=3" while mounting could hint a possible solution, but I'm currently not able to fix this mount option via smb4k. Is there any other way to do this?

Thx!

[Alexander Reinholdt]

I assume that you are using version 3.0.2 of Smb4K.

Please go to the configuration dialog > Mounting > Advanced Mount Settings, tick the "SMB protocol version" check box and choose the appropriate protocol version.

Does mounting work now as expected?

[dyle]

Ah, thank you! That's better! Yes, I'm using 3.0.2. Sorry for not telling this one earlier.

I missed this option. I thought, this is bound to a single bookmarked connection, and not an item for all. But that's clear now. Thx.

Now I can mount quite all connections again, but 2. These two yield in dmesg:

Nov 21 10:44:02 andor kernel: CIFS: Attempting to mount ...<cut on purpose>...
Nov 21 10:44:02 andor kernel: CIFS VFS: Unable to select appropriate authentication method!
Nov 21 10:44:02 andor kernel: CIFS VFS: Send error in SessSetup = -22
Nov 21 10:44:02 andor kernel: CIFS VFS: cifs_mount failed w/return code = -2

I think I search the forum/net for any clue on this one.

Thx!

[dyle]

Ah, switching to NTLMv2 helped but one:

Nov 21 10:57:32 andor kernel: CIFS: Attempting to mount ...<cut on purpose>...
Nov 21 10:57:32 andor kernel: FS-Cache: Duplicate cookie detected
Nov 21 10:57:32 andor kernel: FS-Cache: O-cookie c=0000000002d5496a [p=0000000086fe7cc4 fl=222 nc=4 na=1]
Nov 21 10:57:32 andor kernel: FS-Cache: O-cookie d=00000000917fd2e9 n=0000000037fcf9db
Nov 21 10:57:32 andor kernel: FS-Cache: O-key=[8] '020001bd0a67fa7a'
Nov 21 10:57:32 andor kernel: FS-Cache: N-cookie c=00000000d13a2fc7 [p=0000000086fe7cc4 fl=2 nc=0 na=1]
Nov 21 10:57:32 andor kernel: FS-Cache: N-cookie d=00000000917fd2e9 n=000000002189898f
Nov 21 10:57:32 andor kernel: FS-Cache: N-key=[8] '020001bd0a67fa7a'
Nov 21 10:57:32 andor kernel: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Nov 21 10:57:32 andor kernel: CIFS VFS: Send error in SessSetup = -13
Nov 21 10:57:32 andor kernel: CIFS VFS: cifs_mount failed w/return code = -13

What is a "duplicate cookie"? Hm...

[dyle]

Seems a known issue not yet solved: https://bugzilla.kernel.org/show_bug.cgi?id=200145

[Alexander Reinholdt]

Hm, I haven't read through the whole conversation in the bug report, but it seems that this does not prevent a SMB share from being mounted!?

In your snippet there is the line

Nov 21 10:57:32 andor kernel: CIFS VFS: cifs_mount failed w/return code = -13

which indicates that the permission was denied. Are the credentials correct?

[dyle]

I'm pretty sure they are. I entered the PW several times.
In Windows 10, I can mount the very same share without any error too.

[Alexander Reinholdt]

Ok. So, it seems we have to wait for the kernel developers to solve this issue...