I'm missing the point about wsdd here. I have a server that advertise itself with mDNS protocol, and specify the service type `_smb._tcp`. This is enough for the server to show up in Gnome File "Other Locations".
When the server is clicked, Gnome File fails to enumerate the shared folders, and displays an empty content. On the serve side, we can see the client attempts to use `NT LANMAN 1.0` and `NT LM 0.12` (aka AMBv1) protocols, which is refused as expected. `smbclient -L server` happily enumerates the share folders using `SMB3_11` protocol. Why does gvfs attempt to use SMBv1? Is there a limitation that prevents from using SMB3_11 to enumerate the shared folders? I don't understand why wsdd help with enumerating shared folders. Can you elaborate? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
