s3:libsmb/cli_np_tstream: use larger buffers to avoid a bug NT4 servers (bug #8195)
commita64603f6633d61036fc6a7e626a4738cfe413b52
authorStefan Metzmacher <metze@samba.org>
Tue, 7 Jun 2011 16:27:41 +0000 (7 18:27 +0200)
committerKarolin Seeger <kseeger@samba.org>
Tue, 14 Jun 2011 18:22:42 +0000 (14 20:22 +0200)
treedfa4fad5145fd038d56216ebfbe8bd5f91dc3e11
parentea2b9ca7d7bacccfcec28a57689fe18d33469c09
s3:libsmb/cli_np_tstream: use larger buffers to avoid a bug NT4 servers (bug #8195)

NT4 servers return NT_STATUS_PIPE_BUSY if we try a SMBtrans
and the SMBwriteX before hasn't transmited the whole DCERPC fragment.

W2K and above is happy with that.

As a result we try to match the behavior of Windows and older Samba clients,
they use write and read buffers of 4280 bytes instead of 1024 bytes.
On Windows only the SMBtrans based read uses 1024 (while we also use 4280
there).

metze

Autobuild-User: Stefan Metzmacher <metze@samba.org>
Autobuild-Date: Tue Jun  7 20:25:32 CEST 2011 on sn-devel-104
(cherry picked from commit c3ac298a1fe4f5cada6d09376e2d4a3df271a093)
source3/libsmb/cli_np_tstream.c