https://bugs.kde.org/show_bug.cgi?id=420578
Bug ID: 420578
Summary: kio-discovery-wsd suffix causes failure connecting to
Windows 10 host using WS-Discovery
Product: kio-extras
Version: 20.04
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Samba
Assignee: plasma-b...@kde.org
Reporter: darknesseats...@aim.com
Target Milestone: ---
SUMMARY
When attempting to connect to a windows machine using the kio-discovery-wsd
method, dolphin will always fail giving the error: "Could not connect to host
for smb://HOSTNAME.kio-discovery-wsd/". Typing in the hostname directly
circumvents the issue.
Giving dolphin focus triggers file examination which results in nothing (a
separate issue?).
STEPS TO REPRODUCE
1. Setup a WS-Discovery enabled fileshare server (i.e., I used windows 10 in
VM)
2. Use Dolphin to find the share (i.e., this will take multiple refresh
attempts)
3. Attempt to connect by browsing with Dolphin.
4. Erase the suffix (i.e., change smb://HOSTNAME.kio-discovery-wsd/ to
smb://HOSTNAME)
5. Instant connection
OBSERVED RESULT
Reproducible, recurring failure to connect when the kio-discovery-wsd suffix is
thrown into the hostname.
EXPECTED RESULT
Browsing a share you can discover would be the ideal outcome.
SOFTWARE/OS VERSIONS
Manjaro Unstable Updated: 2/25/2020
--
You are receiving this mail because:
You are watching all bug changes.
