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.
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' Browse) ;'tester' ;'tester' ;'tester' ;'tester' 0x55ebe2ddf700) , failed=1 (Failed to retrieve share list from server: Network dropped connection on reset)
smb-network: Added new job source 0x55ebe2dd53d0 (GVfsBackendSmb
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'
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'
smb-network: returning (nil)
smb-network: looking up cached server 'vwin10'\'IPC$', user 'WORKGROUP'
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'
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(
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.