[Bug 1892897] Re: Cannot access a Samba file share anymore due to "Failed to retrieve file list from server"
More of an FYI but you will get a "Software caused connection abort" error anytime Nautilus tries to connect to a SMB / Samba server that only uses SMB1. There is no SMB1 ( NT1 ) on the client ( or server ) side in Ubuntu20. There is in Ubuntu 18. SO either enable SMB2/SMB3 on the diskstation or enable SMB1 on the client side of Ubuntu20 by editing smb.conf and adding in the [global] section: client min protocol = NT1 Then reboot. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1892897 Title: Cannot access a Samba file share anymore due to "Failed to retrieve file list from server" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1892897/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
@seb128, If the samba share was created on Ubuntu Server and not on Ubuntu Desktop then without the fix you will not see the samba server through Nautilus. That's because Ubuntu Server does not install avahi-daemon by default. Once installed it's visible outside of "Windows Network" because of avahi: I can see it when I run "avahi-browse -at" and when I select it in Nautilus it resolves to vubsrv1804.local: tester@vub1804:~$ ls -al /run/user/1000/gvfs | grep vubsrv drwx-- 1 tester tester 0 Mar 21 07:37 smb-share:server=vubsrv1804.local,share=public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
I understand. I would however like to make a final note about Linux to Linux samba use - at least in a home network. If the server is running Ubuntu 17.10 or later ( with avahi-daemon installed ) this bug is not relevant because the samba client isn't using gvfsd-smb-browse. The sever automatically publishes its presence with the default "multicast dns register = yes" parameter in samba. All Linux machines as well as any MacOS box will see the host automatically using Avahi / Bonjour under "Other Locations" directly without having to go through Windows Network. Under these conditions the client can use SMB3 to connect not SMB1 because gvfsd-smb-browse isn't getting in the way. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
Here's a different perspective. Accessing the Win10 machine again: tester@vub1904:~$ smbclient -L vwin10 -U smbuser Unable to initialize messaging context Enter WORKGROUP\smbuser's password: Sharename Type Comment - --- ADMIN$ Disk Remote Admin C$ Disk Default share Documents Disk IPC$IPC Remote IPC print$ Disk Printer Drivers Shared Disk Users Disk Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_CONNECTION_RESET Unable to connect with SMB1 -- no workgroup available tester@vub1904:~$ smbclient //vwin10/Shared -U smbuser Unable to initialize messaging context Enter WORKGROUP\smbuser's password: Try "help" to get a list of possible commands. smb: \> And the equivalent of smbstatus on Windows: Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. PS C:\WINDOWS\system32> Get-SmbSession | Select Dialect,ClientComputerName Dialect ClientComputerName --- -- 3.1.1 192.168.1.177 smbclient -L automatically goes to SMB1 to get the share listing then tells me it cannot connect to these which makes sense in that state. Yet I can use smbclient itself to access the share if I specify it. This is what gvfsd-smb-browse needs to do. Drop down to NT1 to get the share list which it's doing now then release it and allow the normal smb negotiation to take place. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
smbclient -L, "gio mount smb://server/share ', even just specifying smb://server/share in the location bar in Nautilus works just like you would expect. It's only the gvfsd-smb-browse process that's messed up. As far as it being a related but different problem Well I reckon it all depends on what you mean by fixed. The original issue was you couldn't get a listing of samba hosts in Nautilus so yes that issue is fixed. But why did we want to get the list in the first place? I would argue so that you could gain access to those hosts from the same process and here it only applies to hosts that still allow NT1 / SMB1. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
Your reference to the Linux Samba Server command: smbstatus got me thinking what would happen if I disabled NT1 on a Linux Samba server by stipulating "server min protocol = SMB2" and using Windows Network > ... to connect. The exact same thing happens as when trying to connect to a Win10 machine that's disabled SMBv1. It a different error message: Invalid Argument ( Linux Server ) vs Network dropped connection on reset ( Windows Server ) but the affect is the same. Connection to the host isn't possible through gvfsd-smb- browse. If I reset the Linux server by removing server min protocol = SMB2 it all works because now NT1 was restored. Maybe I'm reading too much into your quote: "Let's force NT1 using the newly added smbc_setOptionProtocols API if available. But force this only when neither hostname, nor IP address is used. This among others prevents complete breakage if NT1 is disabled on server." Is it possible they knew this would happen? Linux doesn't disable SMB1 by default in its server but Windows 10 does on new builds. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
My post concerns Ubuntu Disco. I'm guessing Win10 sees the SMBv1 connection, rejects it outright, and never gets to the protocol negotiation phase. As I said this only involves the gvfsd-smb-browse process: Nautilus > Other Locations > Windows Network > Workgroup If I use Connect to Server I can access the Win10 box without changing anything on the WIn10 side. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
There is an issue with this fix that makes it impossible to access a Windows 10 machine that has disabled SMB1 ( NT1 ): smb-network: g_vfs_backend_smb_browse_init: default workgroup = 'NULL' smb-network: Added new job source 0x55ebe2dd53d0 (GVfsBackendSmbBrowse) smb-network: Queued new job 0x55ebe2ddf700 (GVfsJobMount) smb-network: Error resolving “vwin10”: Temporary failure in name resolution smb-network: Forcing NT1 protocol version smb-network: do_mount - URI = smb://vwin10 smb-network: do_mount - try #0 smb-network: looking up cached server 'vwin10'\'IPC$', user 'WORKGROUP';'tester' smb-network: returning (nil) smb-network: auth_callback - anonymous pass smb-network: auth_callback - out: last_user = 'tester', last_domain = 'WORKGROUP' smb-network: looking up cached server 'vwin10'\'IPC$', user 'WORKGROUP';'tester' smb-network: returning (nil) smb-network: looking up cached server 'vwin10'\'IPC$', user 'WORKGROUP';'tester' smb-network: returning (nil) smb-network: auth_callback - anonymous pass smb-network: auth_callback - out: last_user = 'tester', last_domain = 'WORKGROUP' smb-network: looking up cached server 'vwin10'\'IPC$', user 'WORKGROUP';'tester' smb-network: returning (nil) smb-network: do_mount - [smb://vwin10; 0] dir = (nil), cancelled = 0, errno = [102] 'Network dropped connection on reset' smb-network: do_mount - (errno != EPERM && errno != EACCES), cancelled = 0, breaking smb-network: send_reply(0x55ebe2ddf700), failed=1 (Failed to retrieve share list from server: Network dropped connection on reset) My interpretation of the results: ** Despite SMBv1 being disabled on the server end of Win10 it will still broadcast its NetBIOS name to the rest if the network. ** With this fix the Linux client will correctly discover the Win10 box. ** But it is now in the NT1 ( SMBv1 ) state when it tries to access Win10 and Win10 no longer understands SMBv1. Win10 does not prompt for credentials and no negotiation of which smb protocol to use takes place so access is denied. I have two choices at this point if I still want to use a gvfs ( gio ) mount: [1] I can circumvent gvfsd-smb-browse and use Connect to Server to connect to the Win10 machine explicitly. [2] I can enable SMBv1 on the server end of Win10 and then everything works. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
