s3:libsmb/cli_np_tstream: use larger buffers to avoid a bug NT4 servers (bug #8195)
commitc3ac298a1fe4f5cada6d09376e2d4a3df271a093
authorStefan Metzmacher <metze@samba.org>
Tue, 7 Jun 2011 16:27:41 +0000 (7 18:27 +0200)
committerStefan Metzmacher <metze@samba.org>
Tue, 7 Jun 2011 18:25:32 +0000 (7 20:25 +0200)
treed1d0dfe3305cc2879d13eb2eae945e02f101b968
parentcd8dc47bf17d2cdb1558dc6ab49320ba12af8f34
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
source3/libsmb/cli_np_tstream.c