I have now heard from the administrators of the file server to which I
had trouble connecting. It turns out not to be a Windows machine but a
Netapp system running ONTAP 9. This supports SMB 3.1.0 but not 3.1.1,
explaining the problem.
Although I am surprised that smbclient and the Netapp SMB server are
unable to negotiate an automatic downgrade to SMB 3.1.0, I don't think
this problem is worth reporting to the Samba developers. It may be just
how the SMB protocol works.
I won't close this bug myself because David Sanders reported seeing
similar problems when connecting to a Windows 10 SMB server. If someone
else wants to close it, however, I will not object.
Matthew
On Fri, 24 Aug 2018 14:55:43 +0200 =?windows-1252?Q?L.P.H._van_Belle?=
<[email protected]> wrote:
Only thing i can suggest atm for this one is post your problem on the samba
list.
If you do, post the windows server version your using also.
And preffered also the linux os and smb.conf ( if needed anonymized ).
This might be a regression or a "still" not fixed bug.
Best regards,
Louis
> -----Oorspronkelijk bericht-----
> Van: Matthew Foulkes [mailto:[email protected]]
> Verzonden: vrijdag 24 augustus 2018 13:56
> Aan: [email protected]; L.P.H. van Belle
> Onderwerp: Re: smbclient failing to connect with default
> protocol SMB3_11
>
> Hi Louis,
>
> Thanks for your help, but this bug does not seem to be quite
> the same as
> any of the ones you listed. I can connect when I specify "client max
> protocol" values of SMB3_10, SMB3_02, SMB2, or NT1, but not
> with SMB3 or
> SMB3_11.
>
> Best wishes, Matthew
>
> --
> **************************************************
> email: [email protected]
> phone: (020) 8286 9910
> **************************************************
>
>
--
******************************************************************
Matthew Foulkes
Department of Physics +44 20 7594 7607
Imperial College London [email protected]
London SW7 2AZ www.imperial.ac.uk/people/wmc.foulkes
******************************************************************
