Re: Gvfs and Server-side SMB copy
- From: Saint Germain <saintger gmail com>
- To: gvfs-list gnome org
- Subject: Re: Gvfs and Server-side SMB copy
- Date: Fri, 28 Oct 2016 13:52:20 +0200
On Fri, 28 Oct 2016 08:04:40 +0100, Ross Lagerwall
<rosslagerwall gmail com> wrote :
On Fri, Oct 28, 2016 at 01:40:27AM +0200, Saint Germain wrote:
I haven't been able to locate Ross gvfs dev branch that he
mentionned on his blog.
As far as I understand, samba server-side copy is only available
with the SMB2 protocol, and gvfs can only connect through SMB1
(NT1) ?
Or did I understand something wrong ?
GVFS can do whatever libsmbclient can do. libsmbclient defaults to
SMB1/NT1 at the moment, but you can change that by setting "max client
protocol = SMB3" in /etc/smbclient.conf (or the user one in your home
dir).
I've tried setting in smb.conf:
min protocol = SMB2
max protocol = SMB3
client min protocol = SMB2
client max protocol = SMB3
However the share is not visible in Nautilus anymore and it cannot
connect to the server.
If I try a normal connection with smbclient:
smbclient //192.168.1.200/user -U user
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
However if I use SMB2, it works:
smbclient //192.168.1.200/user -U user -mSMB2
Domain=[DEBIAN] OS=[] Server=[]
smb: \> quit
My configuration:
- client: Debian Stable + smbclient 4.4.6 (coming from Testing) +
kernel 4.7 (amd64) + gvfs 1.22.2
- server: Debian Stable + samba 4.2.10 + kernel 4.7 (amd64)
As smbclient managed to connect through SMB2 but not gvfs, I thought
that gvfs was not compatible with SMB2 ?
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]