Description of problem: Since the last samba updates, smb4k no longer shows network shares. The only way to connect to a share is to use the "Open Mount Dialog" and enter the path by hand. Version-Release number of selected component (if applicable): smb4k-1.2.1-1.fc23.x86_64 samba-4.3.9-0.fc23.x86_64 How reproducible: always Steps to Reproduce: 1. Start smb4k and click on a workgroup name to scan the network. 2. The workgroup name disappears and no network share is shown, although there are many on the LAN. 3. Actual results: No network shares displayed. Expected results: Additional info: Problem also present with samba 4.3.8.
Let me know if open service samba 139/tcp fix the problem ( https://bugzilla.redhat.com/show_bug.cgi?id=1297235#c0 ) Also maybe this https://bugzilla.samba.org/show_bug.cgi?id=11841#c14 Thanks
samba 4.3.9 is available , can you test it ?
Opening port 139/tcp in firewalld (on several machines) doesn't fix the issue. My machines have all samba 4.3.9 installed.
> Since the last samba updates ... is a samba issue , IMHO.
I built samba 4.4.4 for F23 in copr [1] and it works better . [1] https://copr.fedorainfracloud.org/coprs/sergiomb/builds_for_Stable_Releases/
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
it looks like to be the same problem, IMHO , not it's not worth having 2 open reports. *** This bug has been marked as a duplicate of bug 1292983 ***