Bug 369850

Summary:	Can't browse samba workgroups
Product:	[Frameworks and Libraries] kio-extras	Reporter:	Mattia <mattia.verga>
Component:	default	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	c537705, clearmartin, codestruct, elvis.angelaccio, genesoo77072, mail, nate, rdieter, sebas, tomsk_interface
Priority:	NOR
Version:	5.8.4
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Mattia 2016-10-04 05:41:48 UTC

When I try to enter in Network -> Samba shares by the left panel in Dolphin I get "Unable to find any workgroups in your local network. This might be caused by an enabled firewall.".
However this used to work and I didn't changed anything in my firewall. I can also browse samba shares by pointing directly to IP address of a server (for example if I type in the bar smb://192.168.1.200 it opens my server) so it's not a firewall problem, I think.

Dolphin 16.08.1
KDE Frameworks 5.26.0
Qt 5.6.1 (compilato con 5.6.1)
Fedora 24 rpms

Reproducible: Always

Comment 1 mail 2016-12-20 15:35:53 UTC

I'm experiencing the same issue. Nautilus is doing it well...

Comment 2 mail 2016-12-20 15:37:55 UTC

Add Info: 

Dolphin Version 16.12.0

KDE Frameworks 5.29.0
Qt 5.7.0 (kompiliert gegen 5.7.0)
Das xcb Fenstersystem

Comment 3 Gregor Mi 2016-12-24 15:21:45 UTC

Same here on openSUSE 42.1 with KDE Plasma 5.8.4

"Unable to find any workgroups in your local network. This might be caused by an enabled firewall."

Firewall is disabled.

Direct URL entry works.

Comment 4 Gregor Mi 2016-12-24 15:28:45 UTC

At least the browsing works, accessing the folder does not work. I use a user from the configured group "users" but the user and password are not excepted. From the machine where I did the share and from another machine. But this is probably a separate issue.

Comment 5 Elvis Angelaccio 2016-12-27 10:07:57 UTC

Moving to kio-extras where smb:// lives.

Comment 6 Nate Graham 2017-06-26 15:22:25 UTC

*** Bug 365055 has been marked as a duplicate of this bug. ***

Comment 7 Nate Graham 2017-10-10 02:14:52 UTC

*** Bug 385513 has been marked as a duplicate of this bug. ***

Comment 8 Martin Kostolný 2017-10-10 09:03:43 UTC

I suspect the last duplicate is about upgrading to samba 4.7.0. I have noticed the issue ("File exists") since upgrading samba from 4.6.7. Commented an already resolved bug in samba bugzilla (related to version 4.7.0):
https://bugzilla.samba.org/show_bug.cgi?id=12863#c16

Please see the comment, it also says that smbclient is able to browse the share. 

But samba devs say they just changed error message. Anyway upgrade of samba is causing this problem in KIO. I think now that it is possible to use libsmbclient the way it succeeds to connect to the SMB share.

Comment 9 Nate Graham 2017-10-20 17:23:44 UTC

So is this resolved in samba 4.7.0, or is this a duplicate of https://bugs.kde.org/show_bug.cgi?id=385708/ Or none of the above? :)

Comment 10 Nate Graham 2017-10-20 17:30:22 UTC

*** Bug 376128 has been marked as a duplicate of this bug. ***

Comment 11 Martin Kostolný 2017-11-16 21:26:47 UTC

My comment was actually about inability to connect to some shares (even when using IP address) after upgrading to samba 4.7.0. That issue got fixed probably in KDE Apps 17.08.3, and probably by You, Nate, thanks!

So I guess this ticket is about something else and I'm unable to replicate this particular issue. I should have made my comment here: https://bugs.kde.org/show_bug.cgi?id=385708/

Comment 12 Nate Graham 2017-11-16 21:29:56 UTC

Excellent, so glad to hear it! I can't reproduce it, either.