Hi Mathieu,
I'm using an up-to-date debian testing/buster installation with
smbclient 2:4.9.4+dfsg-3.
Matthew
On Wed, Feb 27, 2019 at 10:51:23PM +0100, Mathieu Parent wrote:
Le mercredi 27 février 2019, Matthew Foulkes
a écrit :
> I now have a Debian laptop again and can confirm
Le mercredi 27 février 2019, Matthew Foulkes a
écrit :
> I now have a Debian laptop again and can confirm that bug 883939 still
exists. Nothing has changed. As I have already explained, however, the
problem I am experiencing seems to be specific to the (outdated?) ONTAP 9
software running on the
I now have a Debian laptop again and can confirm that bug 883939 still
exists. Nothing has changed. As I have already explained, however, the
problem I am experiencing seems to be specific to the (outdated?) ONTAP
9 software running on the NetApp file server. It may not be worth
attempting to
I agree that it was probably two separate issues.
As I explained in Message #44, my problem appeared to be NetApp
specific. The administrator of the NetApp server to which I was trying
to connect told me it was running ONTAP 9, which supports SMB 3.1.0 but
not SMB 3.1.1. Assuming he was
Le lun. 18 févr. 2019 à 16:06, David Sanders a écrit :
>
> Mattieu,
>
> I just tried connecting to a Windows 10 machine with and without the "client
> max protocol = SMB3_10" directive in my smb.conf.
>
> I can connect without a problem with the directive present, however when I
> comment it
Hi Mathieu,
I am visiting the US until the end of March and do not have access to a
computer running Debian at the moment. Sorry. I will be buying a new
laptop in a couple of weeks and will install Debian when it arrives, but
cannot help you until then.
Regards, Matthew
On Mon, Feb 18,
Mattieu,
I just tried connecting to a Windows 10 machine with and without the
"client max protocol = SMB3_10" directive in my smb.conf.
I can connect without a problem with the directive present, however when
I comment it out I get the following error message:
protocol negotiation failed:
Hello all,
Are you able to reproduce this bug on latest stretch (2:4.5.16+dfsg-1)
and/or latest buster (2:4.9.4+dfsg-3, -2 is ok).
Regards
--
Mathieu Parent
8 matches
Mail list logo