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
