Just to add another voice to the crowd, I'm on Xubuntu 20.04 and I just
ran across this problem myself.
I am using the Nemo file browser, but the same thing occurs with
Nautilus and Thunar. I didn't notice the problem for a long while
because I had three legacy Windows machines on the network (all running
Windows 10 at this point) and had made file browser bookmarks to the
important shares long ago. These bookmarks have continued to work to
this day without issue. I got a new Windows 10 machine a few weeks ago
and was having the problem everyone reports of not being able to connect
("Failed to retrieve share list from server") on the new machine, even
though all the existing bookmarks were still functioning file. All of
the Windows 10 machines were able to see one another without problem.
Then I ran across this thread and tried Bloodyiron's suggestion of
killing the gvfsd-smb-browse process. Immediately I was able to connect
to the new machine using Nemo. I quickly created some needed bookmarks
to the important shares and now I can communicate using the file browser
and expect the new bookmarks to be as reliable as the others. So I
would suggest this bookmark method to others as a workaround.
This supports Craig W's comment about the difference between discovery
and browsing. When I run "smbclient -L //<ip_address> -U <user>", it
reports all of the shares on the target, whether Windows or Linux, with
the closing message: "SMB1 disabled -- no workgroup available" as
expected.
Unfortunately, this is only a one-way solution. All of the legacy
Windows 10 machines can see and access the Samba shares on the Xubuntu
box, but I haven't yet figured out a way to get the new Windows machine
to access these same shares, with or without gvfsd-smb-browse running.
Every connection attempt is rejected and I haven't found useful messages
in the logs. If I figure out a solution, I'll post here, and I'm open
to suggestions.
I agree with the general sentiment that for a service as important as
this, there isn't any real excuse for this thing dragging out for two
years as it has.
--
You received this bug notification because you are a member of Desktop
Packages, 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
Status in gvfs:
Unknown
Status in gvfs package in Ubuntu:
Triaged
Bug description:
After bug #1778322 is fixed (just needs a gvfs rebuild with newer
samba), samba machines will start to show up again in the "windows
network" tab in nautilus. But if a server has disabled the SMB1
protocol, nautilus will show an error when that server is clicked on,
instead of showing the shares list.
Even with SMB1 disabled, it should still be technically possible to
get a share list, since smbclient can do it:
andreas@nsnx:~$ nmblookup -A 192.168.122.101
Looking up status of 192.168.122.101
D-NO-SMB1 <00> - B <ACTIVE>
D-NO-SMB1 <03> - B <ACTIVE>
D-NO-SMB1 <20> - B <ACTIVE>
..__MSBROWSE__. <01> - <GROUP> B <ACTIVE>
WORKGROUP <00> - <GROUP> B <ACTIVE>
WORKGROUP <1d> - B <ACTIVE>
WORKGROUP <1e> - <GROUP> B <ACTIVE>
MAC Address = 00-00-00-00-00-00
andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
WARNING: The "syslog" option is deprecated
Sharename Type Comment
--------- ---- -------
print$ Disk Printer Drivers
pub_no_smb1 Disk
IPC$ IPC IPC Service (d-no-smb1 server (Samba, Ubuntu))
Reconnecting with SMB1 for workgroup listing.
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
Failed to connect with SMB1 -- no workgroup available
andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m
NT1
WARNING: The "syslog" option is deprecated
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m
SMB2
WARNING: The "syslog" option is deprecated
Try "help" to get a list of possible commands.
smb: \> dir
. D 0 Fri May 3 18:16:38 2019
.. D 0 Fri May 3 18:15:24 2019
hello.txt N 21 Fri May 3 18:16:12 2019
hello-from-nsnx.txt A 9 Fri May 3 18:16:38 2019
20509264 blocks of size 1024. 13121800 blocks
available
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
