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 right, this explained most of my problem, except why smbclient was unable to negotiate the use of a mutually supported protocol.

It did look like Samba bug 13009, but I was definitely running 4.7.3. I guess the problem was out-of-date software on the NetApp server.

Matthew


On Wed, Feb 20, 2019 at 09:31:59PM +0100, Mathieu Parent wrote:
Le lun. 18 févr. 2019 à 16:06, David Sanders <da...@sandersweb.net> 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 out I get the following error message:

protocol negotiation failed: NT_STATUS_CONNECTION_RESET

So either there's a bug with this version or something is screwy with the 
configuration on the Windows machine. It's not a big problem for me because the 
work around fixes it.

I am running stretch 9.8 with samba 2:4.5.16+dfsg-1

Thanks for your feedback.

I'm confused because there may be two different problems here.

Matthew Foulkes's "protocol negotiation failed:
NT_STATUS_INVALID_NETWORK_RESPONSE" looks like upstream
https://bugzilla.samba.org/show_bug.cgi?id=13009, against NetApp, and
which is fixed in 4.7.0 (i.e Debian buster), but Matthew's original
report was already 4.7.3.

David Sanders's "protocol negotiation failed:
NT_STATUS_CONNECTION_RESET" is against Windows 10 and is still not
fixed with 2:4.5.16+dfsg-1. Maybe fixed on buster (2:4.9.4+dfsg-3)? It
looks like https://bugzilla.samba.org/show_bug.cgi?id=12863 fixed in
4.7.12.


Regards
--
Mathieu Parent

--
**************************************************
 email: m.foul...@blueyonder.co.uk
 phone: 07905 505676
**************************************************

Reply via email to