Bug 431052

Summary: SMB: better error message for SMBv1
Product: [Frameworks and Libraries] kio-extras Reporter: Peter Eszlari <peter.eszlari>
Component: SambaAssignee: Plasma Bugs List <plasma-bugs>
Status: REPORTED ---    
Severity: normal CC: kfm-devel, ltsallas, nate, sitter
Priority: NOR Keywords: usability
Version: 20.11.80   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Peter Eszlari 2021-01-02 09:17:40 UTC 
SUMMARY

I have an old device (Western Digital WDTV Live Media Player), that only supports SMBv1. In Samba 4.11 the default minimum protocol version was increased to SMB2. Trying to access the share results in a unhelpful error message.

STEPS TO REPRODUCE
1. navigate to Network > Shared Folders (SMB)
2. try to open share


OBSERVED RESULT

error message:

"Connection to host wdtvlive.local is broken."

EXPECTED RESULT

something like this as an error message:

"Support for SMB version 1 is not enabled."


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.20
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-58-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i3-4130 CPU @ 3.40GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4400
Comment 1 Harald Sitter 2021-01-27 13:25:52 UTC 
How would one get from "the host doesn't want to talk to us" to know that it speaks smb1? Mind you, the minimium protocol forbids speaking SMB1.
Comment 2 Peter Eszlari 2021-01-27 21:48:16 UTC 
When I don't enable SMBv1 in /etc/samba/smb.conf and try to access the share in Thunar, I get:

gvfsd[1940]: smbXcli_negprot_smb1_done: No compatible protocol selected by server.
Comment 3 Christoph Feck 2021-02-08 20:12:57 UTC 
New information was added; changing status for inspection.
Comment 4 Lefteris Tsallas 2021-12-30 09:50:11 UTC 
Had the same issue with and old NAS, took my a while to understand what was happening. 
The error response I got from smbclient was a bit more helpful "protocol negotiation failed: NT_STATUS_CONNECTION_DISCONNECTED" 

This allowed me to search for what the error is about and find the solution.
I would say that the issue is not about specifically the SMBv1  error, but rather dolphin being able to propagate the error response to the UI
Comment 5 Peter Eszlari 2023-12-29 01:01:23 UTC 
(In reply to Harald Sitter from comment #1)
> How would one get from "the host doesn't want to talk to us" to know that it
> speaks smb1? Mind you, the minimium protocol forbids speaking SMB1.

I don't if adding a dependency on nmap would be too much, but apparently it can scan for this:

https://nmap.org/nsedoc/scripts/smb-protocols.html