[kio-extras] [Bug 421624] refactor modern discovery out of NB discovery
Harald Sitter
bugzilla_noreply at kde.org
Mon May 18 16:16:44 BST 2020
https://bugs.kde.org/show_bug.cgi?id=421624
Harald Sitter <sitter at kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
Summary|Wrong and misleading |refactor modern discovery
|message when navigating to |out of NB discovery
|samba shares list in |
|Dolphin |
--- Comment #9 from Harald Sitter <sitter at kde.org> ---
Alrighty, so, I think this is a configuration problem.
What is going on is that libsmbclient sends a netbios broadcast but appears to
get no response which I am guessing means that there is simply no server in the
entire network that has netbios enabled (or you have a firewall and that
filters all netbios traffic). This then causes the error you see. On top of
that, as mentioned, our modern replacements for netbios also do not run when
the netbios query errors out.
I'm going to look into a way to detangle this on our end but that only helps
iff your server has DNSSD or WSD enabled, neither are builtin into samba 3.6 I
think, so you'll either want to upgrade or look into having avahi (on the
server) and manually define an smb service through that. If all else fails you
can also have another server play "proxy" for the discovery see this comment
for details https://bugs.kde.org/show_bug.cgi?id=418417#c1
If you actually want to have NB-based discovery, which is kind of required if
you have SMB1-exclusive clients, your server is probably misconfigured (as-in:
not running nmbd; or a firewall gets in the way of the NB traffic).
In short: the caveat heer is that all this depends on what you expect to happen
here.
- If you think netbios should work, which is the more legacy windows tech, then
something is wrong with the server-side setup as no NB replies arrive on the
client
- If you think dnssd/wsd should work then this is a bug in kio-extras which
I'll look into. Your server needs to be exposed on one of those discovery
services though
Regardless I am sure that in the meantime if you simply run nmbd *anywhere* in
your network, even localhost, it should make the error go away.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list