[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
@BloodyIron, please see: https://github.com/christgau/wsdd I suggest you install as it is a significantly better work-around than constantly killing the daemon. It is intended to be released in the next Debian (bookworm) release as a package, I do not know if Ubuntu will also be including it in their next release. Whether Nautilus will use it or not, I could not answer to that - I have long since switched to using Thunar without any issues. With regards to "If restarting it 'fixers' it, then why on earth does it break in the first place?" I suggest you see one of the replies here: https://gitlab.gnome.org/GNOME/gvfs/-/issues/307 and further reading here: https://gitlab.gnome.org/GNOME/gvfs/-/issues/506 ** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #307 https://gitlab.gnome.org/GNOME/gvfs/-/issues/307 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
My apologies for sidetracking this far trying to explain differences between discovery and browsing but there seems to be a lot of mixing the 2 as one. The fact that you have "discovered" a server you wish to "browse" is irrelivant for this bug (afaik you shouldn't have been able to discover it as there are currently no working mechanisms to do so in LTS versions judging from the open bug reports). If however you are experiencing a crash whilst attempting to browse a share of the discovered host, that is relevant and is to do with the way SMB protocol versions themselves are being handled. WRT the rest of the discussion: SMBv1 leveraged NetBios to do discovery, (as did WINS which was a fallback discovery method). With SMBv1 removed/disabled, all of the NetBios discovery is also removed/disabled. Therefore, a discovery protocol is needed. Enter WSD. SMBv2 and SMBv3 use WSD to discover hosts on the network, (incidentally WSD was designed for SMBv2 during the development of Vista to remove the dependancy on NetBios). If you know the address of a host serving SMBv2 or SMBv3 already (via WSD, any other discovery protocol, off by heart), you can just do an SMB request against that address: smbclient --list=<> --user=Anonymous -N >The discoverability and connectivity works when the process is terminated and >restarted. Clearly this is achievable. > Yes, netbios was used previously, but clearly after killing the process I can > reach them without SMB v1, just not after the first boot. This is still probably nothing more than a cached entry, start-up check of previously known hosts, or initial broadcast. Some of which may or may not be unintentional from a security perspective, so as @seb128 said, file another bug report against them if you so wish. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
In the very same article you linked: https://docs.microsoft.com/en-us /windows-server/storage/file-server/troubleshoot/smbv1-not-installed-by- default-in-windows With SMBv1 being removed, Network Browser (which depended on SMBv1) was removed, all of which relied on NetBios being used for discovery. (Hence, NetBios is dead, long live NetBios). Microsoft's replacement for NetBios discovery is *drumroll please*: WSD. I'm completely speculating here but: Your initial start up effect is probably gvfsd-smbd doing something like a Browser Tree scan of last known hosts. This actively goes to the host asking about available protocols, shares etc. This is NOT discovery. You could argue "well if it already knew about it, how does it lose it?" and that is a fair question, to which the answer might well be "Don't want to do an expensive back n forth poll, would rather use a discovery protocol", and now we are back to the discussion of needing a discovery protocol: WSD. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Not to put too fine a point on it, but actually that is exactly what this requires. Microsoft phased out the SMBv1 protocol, (NetBios is dead, long live NetBios), in favour of their new protocol: Web Services Dynamic Discovery (WSD). There has been a lot of discussion and work as to exactly HOW WSD should be implemented for SAMBA and gvfs and what to do in future if Microsoft do another flip of the switch. Granted this has taken a lot of time, but as previously mentioned, all of this discussion and development is dependent on people gratuitously handing over their free time. If you want up to date support and to demand for things to be done, might I politely suggest you fork out for a Red Hat enterprise subscription. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
