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
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 0x55ebe
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
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
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
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$
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 automatical
@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
ava
