Bug 309841 - Can't browse work groups when the master browser is on the gateway, not the server with the shares
Summary: Can't browse work groups when the master browser is on the gateway, not the s...
Status: RESOLVED WORKSFORME
Alias: None
Product: kio
Classification: Unmaintained
Component: smb (show other bugs)
Version: 4.9.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-11-10 07:52 UTC by Alexander
Modified: 2018-10-29 02:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Example video (910.36 KB, video/ogg)
2012-11-10 07:54 UTC, Alexander
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander 2012-11-10 07:52:56 UTC
Hi, look at the video I've attached. When trying to access samba shares dolphin says "Can't find work groups in my local network. Perhaps firewall block it." (that's not an original message, translated by me). Although it works if I specify IP address (given from network manager).

Tried to restart smbd service — no effect.
Tried to restart nmbd service — no effect.
Tried to restart smbd service — and it works now.

Each time, to access samba work groups, I need to restart nmbd first and then restart smbd.

I am not sure, though, if this is related to Dolphin, but as you can see other PCs are accessible by their IP addresses.

Reproducible: Always

Steps to Reproduce:
1. Reboot your PC
2. Log in to KDE
3. Open network → samba shares
4. Dolphin display this error "Can't find work groups in my local network..."
5. Restart nmbd and then smbd services
6. Work groups are visible now.
Comment 1 Alexander 2012-11-10 07:54:03 UTC
Created attachment 75147 [details]
Example video
Comment 2 Frank Reininghaus 2012-11-29 06:10:44 UTC
Thanks for the bug report! I think that this is related to the SMB kioslave.
Comment 3 Alexander 2012-11-29 07:11:09 UTC
Hi, you are welcome :) I think this also might be an issue with smb/nmb, something could be wrong with my samba setting as well. Can you reproduce the behavior from the video attached?

I've also opened a ticket here https://bugs.archlinux.org/task/32802 and added my smb config.
Comment 4 Frank Reininghaus 2012-11-29 07:14:56 UTC
(In reply to comment #3)
> Can you reproduce the behavior from the video attached?

I don't have access to any SMB shares, sorry.
Comment 5 Alexander 2013-06-28 07:31:38 UTC
This is only happening for me when the samba server is not a master browser. Just confirmed that this way:

1. Powered off entire home network and disconnected all devices.
2. Disallowed my local samba to participate in a master browser election.
3. Powered on my home router and also powered on a notebook with M$ 7.
4. Since the router also has a samba server on board which has a higher priority than M$ 7 and thus becomes a master browser.
5. I can browse my network from the notebook but in dolphin I see an error messages that it is unable to find work groups/ 
6. Edited my smb.conf and forced my local server to be a master browser (set os level = 255 and preferred master = yes)
7. Reloaded smb.conf and forced the election
8. Restarted dolphin and my network is browseable now

The problem is in that my PC is not always up and other network devices are often see the network unavailable (when I power on/off my PC it causes an election to happen). So I want to have my router as a master and local browser. But in that case I can't browse network from samba machines.
Comment 6 Nate Graham 2018-06-28 17:54:22 UTC
If your PC is off, you wouldn't be able to browse shares anyway, right?

What is it that you expect to happen here?
Comment 7 Andrew Crouthamel 2018-09-28 03:16:28 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-10-29 02:24:23 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!