Jonathan N. Little
2017-10-17 18:09:53 UTC
I only have one lousy Windows left and since next update will disable
SMB1 I decided to preemptively test. Disabled SMB1 on winbox so now
requires SMB2 or SMB3. How to you get Nautilus to use SMB3 to connect to
Windows shares? I can do it via smbclient:
smbclient smb://winbox/shared -m SMB3
A1-Skippy! But Nautilus fails either by bookmark
smb://WORKGROUP;***@winbox/shared
or trying to use Go > Connect to server.
If I reenable SMB1 on the winbox then there is no problem connecting. So
far all I can find is how to get Windows clients to connect to Linux
server shares (easy), but not the reverse. Using workgroup not a domain.
The only way I can think is to mount in fstab where I can specify
protocol with 'ver=3.0'. Is there some setting in gvfs or something?
SMB1 I decided to preemptively test. Disabled SMB1 on winbox so now
requires SMB2 or SMB3. How to you get Nautilus to use SMB3 to connect to
Windows shares? I can do it via smbclient:
smbclient smb://winbox/shared -m SMB3
A1-Skippy! But Nautilus fails either by bookmark
smb://WORKGROUP;***@winbox/shared
or trying to use Go > Connect to server.
If I reenable SMB1 on the winbox then there is no problem connecting. So
far all I can find is how to get Windows clients to connect to Linux
server shares (easy), but not the reverse. Using workgroup not a domain.
The only way I can think is to mount in fstab where I can specify
protocol with 'ver=3.0'. Is there some setting in gvfs or something?
--
Take care,
Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
Take care,
Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com