s3: libsmbclient: Fix hard-coded connection error return of ETIMEDOUT.
authorJeremy Allison <jra@samba.org>
Wed, 2 May 2018 18:19:31 +0000 (11:19 -0700)
committerJeremy Allison <jra@samba.org>
Thu, 3 May 2018 00:42:20 +0000 (02:42 +0200)
commit795ec751ac5f6e58966385bec25063c4af4f185d
tree5f3fed6836ce5612b60a3573fc9ed550fbec089f
parent0c78aa1f3a6eb9c08c2fdd10c304d6192cb1b6c2
s3: libsmbclient: Fix hard-coded connection error return of ETIMEDOUT.

We shouldn't hard-code the connection error as ETIMEDOUT when
we have a perfectly good NT_STATUS to map from.

Found by the ChromeOS guys trying to connect an SMB2-only client
to an SMB1-only supporting server.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=13419

Signed-off-by: Jeremy Allison <jra@samba.org>
Reviewed-by: Volker Lendecke <Volker.Lendecke@SerNet.DE>
Autobuild-User(master): Jeremy Allison <jra@samba.org>
Autobuild-Date(master): Thu May  3 02:42:20 CEST 2018 on sn-devel-144
source3/libsmb/libsmb_server.c