https://bugs.kde.org/show_bug.cgi?id=420188
--- Comment #4 from Harald Sitter <sit...@kde.org> --- (In reply to Nate Graham from comment #2) > (In reply to Harald Sitter from comment #1) > > kf5.kio.core: "Can't load /etc/samba/smb.conf - run testparm to debug it\n" > > > > It seems you or your distro broke your smb config which would result in > > defaults getting used and the samba defaults are to not speak the deprecated > > SMB1 protocol hence you cannot talk to the router with only SMB1 support. > Maybe we should have Dolphin show a user-comprehensible error message when > this is the case? Ideally yes, but, we don't know that it's an SMB1 problem. When SMB1 is disabled libsmbc isn't allowed to talk SMB1 with the remote. A remote that only speaks SMB1 isn't really distinguishable from a remote that has a HTTP server run on that port for example, they both speak gibberish from libsmbc's POV. Windows 10 has fundamentally the same problem. The best we could do is make the error more descriptive. Patches welcome ;) I expect we'll also need an entire wiki page or docs page somewhere explaining the entire mess though. Telling people that this may be because their device only supports SMB1 isn't that useful without explaining what can be done about it. (In reply to Jack from comment #3) > I have never modified or touched that file on my PC (it never existed) or > even enabled Samba to talk with SMB1, it always worked out of the box. You'll want to talk to your distribution. We haven't changed anything there, and in fact it's always been libsmbclient's defaults that decided whether or not SMB1 is supported (it has been off by default for years now though). -- You are receiving this mail because: You are watching all bug changes.
