Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*TCPWindowsize\s+on\s+NT\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*TCPWindowsize\s+on\s+NT\s*$/: 3 ]

Total 3 documents matching your query.

1. TCPWindowsize on NT (score: 1): Author: Kyle Payne <payne AT BERBEE DOT COM>; Date: Thu, 2 Dec 1999 10:08:56 -0600; ADSMers, Many of you who implement ADSM on NT for either the client or server know of the flash that states you should set TCPWINDOWSIZE to 63 and not 64 (as the tuning guide suggests) for NT clients; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-12/msg00054.html (11,358 bytes)
2. Re: TCPWindowsize on NT (score: 1): Author: Chris Zaremba <zaremba AT US.IBM DOT COM>; Date: Fri, 3 Dec 1999 11:38:14 -0500; Sorry for the long append, but here is an excellent explanation of the subject courtesy of Charlie Nichols, one of our performance guys... For starters, I include some relevant sections from the Micr; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-12/msg00123.html (17,598 bytes)
3. Re: TCPWindowsize on NT (score: 1): Author: "Remeta, Mark" <MRemeta AT SELIGMANDATA DOT COM>; Date: Mon, 6 Dec 1999 15:55:18 -0500; how does the parameter TCPBUFFSIZE come into play? Should it be a multiple of TCPWINDOWSIZE??? Thanks, Mark; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-12/msg00149.html (10,140 bytes)

Current List: 1 - 3
Page: [1]