samba - Feb 2019 - smbclient error talking to Netapp with SMB 3.11 / Samba 4.7.11

Hi,

we have a situation where access to a share on some Netapp box
fails with “client max protocol” set to SMB3_11 (or unset):

    protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

With a protocol max set to SMB3_10 or SMB3_02 the login prompt is
reached and subsequent file access is succeeds:

     negotiated dialect[SMB3_00] against server[192.168.42.42]
    got OID=1.2.840.48018.1.2.2
    Enter DOM.AIN\foobar's password:

The symptoms resemble that of this bug:
https://bugzilla.samba.org/show_bug.cgi?id=13009 but the protocol
versions differ. Also we’re pretty much on vanilla 4.7.11 so we
have commit 81f31fd509.

We have packet captures of the three protocol versions mentioned
and (not really conclusive to me) debug output of the client. Due
to confidentiality reasons I can’t share them but I will try and
answer any questions about the dumps. Also this is a customer’s
system so we’re very limited in our means to run tests.

Any idea what might be the issue?

Thanks,
Philipp

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL:
<http://lists.samba.org/pipermail/samba/attachments/20190213/3c649f5f/signature.sig>

Hai Philipp,


DOM.AIN\foobar's password:
^^^^^^^^ 

No dot is allowed in the NTDOM 
Fix that first, then try again.



Greetz, 

Loius

 
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Philipp Gesang via samba
> Verzonden: woensdag 13 februari 2019 16:14
> Aan: samba at lists.samba.org
> Onderwerp: [Samba] smbclient error talking to Netapp with SMB 
> 3.11 / Samba 4.7.11
> 
> Hi,
> 
> we have a situation where access to a share on some Netapp box
> fails with “client max protocol” set to SMB3_11 (or unset):
> 
>     protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
> 
> With a protocol max set to SMB3_10 or SMB3_02 the login prompt is
> reached and subsequent file access is succeeds:
> 
>      negotiated dialect[SMB3_00] against server[192.168.42.42]
>     got OID=1.2.840.48018.1.2.2
>     Enter DOM.AIN\foobar's password:
> 
> The symptoms resemble that of this bug:
> https://bugzilla.samba.org/show_bug.cgi?id=13009 but the protocol
> versions differ. Also we’re pretty much on vanilla 4.7.11 so we
> have commit 81f31fd509.
> 
> We have packet captures of the three protocol versions mentioned
> and (not really conclusive to me) debug output of the client. Due
> to confidentiality reasons I can’t share them but I will try and
> answer any questions about the dumps. Also this is a customer’s
> system so we’re very limited in our means to run tests.
> 
> Any idea what might be the issue?
> 
> Thanks,
> Philipp
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

Hi Louis,

thanks for your reply.

-<| Quoting L.P.H. van Belle via samba <belle at bazuin.nl>, on
Wednesday, 2019-02-13 04:59:55 PM |>-
> 
> DOM.AIN\foobar's password:
> ^^^^^^^^ 
> 
> No dot is allowed in the NTDOM 
> Fix that first, then try again.
That’s the output when logon succeeds though nor does the value
seem to matter anywhere else. This is just Samba acting as a SMB
client without any domain membership and all that jazz.

Unfortunately we can’t just arbitrarily access the box in
question so before I schedule a call with the customer I’d
rather gather some more feedback first.

Thanks,
Philipp

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL:
<http://lists.samba.org/pipermail/samba/attachments/20190213/629004a5/signature.sig>