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)
committerKarolin Seeger <kseeger@samba.org>
Mon, 7 May 2018 12:25:28 +0000 (14:25 +0200)
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

(cherry picked from commit 795ec751ac5f6e58966385bec25063c4af4f185d)

Autobuild-User(v4-8-test): Karolin Seeger <kseeger@samba.org>
Autobuild-Date(v4-8-test): Mon May  7 14:25:28 CEST 2018 on sn-devel-144

source3/libsmb/libsmb_server.c

index e6067be2013025b8517fef912e44c548cb807d75..67dfcf72327dc4d2e8e77f83bc2ad70e3ee106cd 100644 (file)
@@ -500,7 +500,7 @@ SMBC_server_internal(TALLOC_CTX *ctx,
                                 lp_client_max_protocol());
        if (!NT_STATUS_IS_OK(status)) {
                cli_shutdown(c);
-               errno = ETIMEDOUT;
+               errno = map_errno_from_nt_status(status);
                return NULL;
        }