Bug 423320

Summary:	Dolphin doesn't discover machine's own Samba server
Product:	[Applications] dolphin	Reporter:	tempel.julian
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	kfm-devel, nate, sitter
Priority:	NOR
Version:	20.04.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description tempel.julian 2020-06-21 14:05:24 UTC

SUMMARY
When browsing discovered SMB shares (smb://), Dolphin does not show the server running on the same system.

STEPS TO REPRODUCE
1. Install Samba and configure it like this:

[global]
workgroup = workgroup
server string = ""
map to guest = bad user

[network]
path = /home/user/network/
read only = no
guest ok = yes
force user = user

Start smb and nmb systemd units.

2. Start dolphin and go to smb://

OBSERVED RESULT
The used/same system does not show up there.

EXPECTED RESULT
It should show up there, it did so in the past.

It's still possible to access the same machine's Samba server by manually entering the machines name in Dolphin's path field, e.g.
smb://*@user-linux/network/

So it seems it's really just the discovery that doesn't recognize it for some reason.
Other Windows clients in the same network discover the share without issues. I don't have other Linux clients to test with though.


SOFTWARE/OS VERSIONS
Linux 5.7.4
KDE Plasma Version: 5.19.1
KDE Frameworks Version: 5.71.0
Qt Version: 5.15

ADDITIONAL INFORMATION
samba 4.12.3

Comment 1 Nate Graham 2020-06-22 16:24:01 UTC

I think this might be intentional. What's the use case for discovering your own local samba server when browsing the network?

Comment 2 Harald Sitter 2020-06-22 16:42:45 UTC

Works for me. It's not intentionally not working as in: it's more work to make it not work than to just treat localhost as any other host ;)

Report needs a debug log though: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Debugging_IOSlaves/Debugging_kio_smb#Reporting_Bugs

Also, do make sure avahi is installed/configured/enabled.

Comment 3 tempel.julian 2020-06-22 17:06:20 UTC

You are right, I needed to enable avahi and configure it for hostname resolution.
Weird, I think I never did this before and remember it working regardless. Well, might be mistaken though.

Anyhow, thanks for all the SMB improvements (also to the guys who worked on kio-fuse)!

Comment 4 tempel.julian 2020-10-08 23:28:50 UTC

Just for the record: The missing self-discovery was due to tighter client protocol requirements by recent Samba versions, actually the workgroup as a whole was missing.