Launchpad has imported 9 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=392447.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2018-03-28T11:37:42+00:00 Suse wrote: Dolphin doesn't show any samba share. smb:// and smb://workgroup/ are empty. However, smbtree is always working. If made all test with deactivated firewall. Entering a specific share like smb://twvm1/ is always working. I've made many test with different distributions and software versions: -------- DOES NOT WORK: Tumbleweed with: Plasma: 5.12.3 Framework: 5.44.0 Applications: 17.12.3 Samba: 4.7.6 Fedora 27 with Plasma: 5.12.2 Framework: 5.44.0 Applications: 17.12.2 Samba: 4.7.6 Neon with Plasma: 5.12.3 Framework: 5.44.0 Applications: 17.12.3 Samba 4.3.11-Ubuntu extra file: ~/.smb/smb.conf [global] client max protocol = SMB2 ---------- WORKS: Neon with Plasma: 5.12.3 Framework: 5.44.0 Applications: 17.12.3 Samba 4.3.11-Ubuntu Tumbleweed with: Plasma: 5.12.3 Framework: 5.44.0 Applications: 17.12.3 Samba: 4.6.16 (Downgraded with repo home:j-engel) Tumbleweed with: Plasma: 5.12.3 Framework: 5.44.0 Applications: 17.12.3 Samba: 4.7.6 extra file: ~/.smb/smb.conf [global] client max protocol = NT1 =============== Conclusion: As soon as the samba protocol newer NT1 (e.g. SMB2) is used, then dolphin doesn't show the samba shares. You can force the usage of NT1 via: - Samba < 4.7 or adding the extra file ~/.smb/smb.conf [global] client max protocol = NT1 You can force the usage of SMB2 or SMB3 via: - Samba >= 4.7 or adding the extra file ~/.smb/smb.conf [global] client max protocol = SMB3 Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/0 ------------------------------------------------------------------------ On 2018-03-28T11:40:01+00:00 Suse wrote: Created attachment 111699 journalctl of samba 4.7.6 This log is from a samba 4.7.6 machine where the SMB2 or SMB3 protocol is used. I've clicked on "samba shares" in dophin (= smb://). Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/1 ------------------------------------------------------------------------ On 2018-04-30T15:58:54+00:00 ben van 't ende wrote: I added the extra file ~/.smb/smb.conf [global] client max protocol = NT1 For Kubuntu 18.04 (Samba version 4.7.6-Ubuntu) to get it to work Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/10 ------------------------------------------------------------------------ On 2018-05-05T18:01:15+00:00 Strangiato Xanadu wrote: I can not confirm. My two computers run Arch Linux pc A: kde plasma 5.12.5, frameworks 5.45, dolphin 18.04, samba 4.8.1 pc B: Gnome 3.28.1, nautilus 3.28.1, samba 4.8.1 Both computers have "[global] client max protocol = SMB2" in their smb.conf file. Dolphin from pc A shows the samba shares from pc B. Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/21 ------------------------------------------------------------------------ On 2018-05-06T00:32:32+00:00 Strangiato Xanadu wrote: *** Bug 393880 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/22 ------------------------------------------------------------------------ On 2018-06-23T10:08:22+00:00 Y-dev-4 wrote: I can confirm this behavior with openSUSE Leap 15.0 (Plasma 5.12.5, Frameworks 5.45.0) on the client and Samba 4.6.14 on the server. Dolphin shows nothing with smb:// if I go to the share directly in Dolphin it works. With smbtree the shares are showing correctly. The following file on the client helps, thank you: ~/.smb/smb.conf [global] client max protocol = NT1 But it would be better do solve this issue in the smb kio plugin directly. Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/25 ------------------------------------------------------------------------ On 2018-07-20T21:06:01+00:00 Nate-b wrote: *** Bug 392803 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/26 ------------------------------------------------------------------------ On 2018-07-20T21:06:02+00:00 Nate-b wrote: *** Bug 388000 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/27 ------------------------------------------------------------------------ On 2018-07-20T21:14:38+00:00 Nate-b wrote: Migrating information from a duped bug: The SMB1 protocol is deprecated and Microsoft strongly urges people not to use it. Windows 2016 server does not support it, and Windows 10 only supports it if it's used within the first 15 days (!). It's clearly not going to work in the future. [1] Ubuntu 18.04 ships with Samba 4.7.6, which uses SMB2 by default. Network discovery is provided by the SMB1 protocol. [2] In SMB2 and later, network discovery has to be provided by a separate protocol, WS-Discovery. There doesn't seem to be any Linux support for WS-Discovery, either in the Samba project or elsewhere[3] The Smbtree command line tool intelligently downgrades itself to using the old SMB1 version for the purposes of browsing.[4] Connections are actually made using the newer, more secure version. libsamba (the actual library that we use) does not have the same behavior. --- Distros have been left with two bad options: stay with the insecure and deprecated SMB1 protocol to preserve the network discovery feature for many (but not all) SMB resources, or move to the secure and supported version of the SMB protocol and lose network discovery for all SMB resources. Ubuntu and OpenSUSE chose the latter. You can make the other choice for yourself by adding "client max version = NT" to /etc/samba/smb.conf. --- KDE's options are as follows: 1. Wait for Samba to support the newer WS-Discovery protocol for browsing 2. Implement WS-Discovery support ourselves, perhaps taking inspiration or re-using an existing approach. [5][6] [1] https://blogs.technet.microsoft.com/filecab/2016/09/16/stop-using-smb1/ [2] https://dev.solus-project.com/T1223#91845 [3] https://dev.solus-project.com/T1223#92389 [4] https://bugzilla.samba.org/show_bug.cgi?id=12876#c2 [5] https://nmap.org/nsedoc/scripts/wsdd-discover.html [6] http://www.dankulp.com/blog/2013/05/apache-cxf-and-ws-discovery/ Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/28 ** Changed in: nautilus Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1767454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
