On a W2k machine, I've tried several different recommendations for adjusting
the TCP receive window size. None of them, including those directly from
Microsoft, seem to have any impact. I'm capturing my own traffic and my
advertised window is always in the 64k range.
I've tried editing the \tcpi
Are you trying to make the window smaller?
rgds
Marc
s vermill wrote:
>
> On a W2k machine, I've tried several different recommendations for
adjusting
> the TCP receive window size. None of them, including those directly from
> Microsoft, seem to have any impact. I'm capturing my own traffic an
Marc Thach Xuan Ky wrote:
>
> Are you trying to make the window smaller?
> rgds
> Marc
Yes. I was hoping to set up a demonstration on the impact of high
bandwidth*delay product networks without actually having a high
bandwidth*delay product network. By artifically enforcing a small rcv
window,
On Tue, 2002-12-17 at 14:34, s vermill wrote:
> On a W2k machine, I've tried several different recommendations for
adjusting
> the TCP receive window size. None of them, including those directly from
> Microsoft, seem to have any impact. I'm capturing my own traffic and my
> advertised window is
Steve Dispensa wrote:
>
> On Tue, 2002-12-17 at 14:34, s vermill wrote:
> > On a W2k machine, I've tried several different
> recommendations for adjusting
> > the TCP receive window size. None of them, including those
> directly from
> > Microsoft, seem to have any impact. I'm capturing my own
>
: Perhaps O/T: Window TCP Rcv Window [7:59400]
Marc Thach Xuan Ky wrote:
>
> Are you trying to make the window smaller?
> rgds
> Marc
Yes. I was hoping to set up a demonstration on the impact of high
bandwidth*delay product networks without actually having a high
bandwidth*delay pro
Scott,
A clue from this webpage:
http://www.psc.edu/networking/perf_tune.html
Describing Win98 it says "DefaultRcvWindow is a string type and the
value describes the default receive windowsize for the TCP stack.
Otherwise the windowsize has to be programmed in apps with setsockopt."
Perhaps the app
sier in that world. It's on my list
of technologies to master. Sigh...
>
> -Original Message-
> From: s vermill [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, 18 December 2002 6:40 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Perhaps O/T: Window TCP Rcv Window [7:5940
Marc Thach Xuan Ky wrote:
>
> Scott,
> A clue from this webpage:
> http://www.psc.edu/networking/perf_tune.html
> Describing Win98 it says "DefaultRcvWindow is a string type and
> the
> value describes the default receive windowsize for the TCP
> stack.
> Otherwise the windowsize has to be program
e 64kbps.
>
> Rik
>
> -Original Message-
> From: s vermill [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, 18 December 2002 6:40 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Perhaps O/T: Window TCP Rcv Window [7:59400]
>
> Marc Thach Xuan Ky wrote:
> >
> >
s vermill wrote:
>
> Group:
>
> On a W2k machine, I've tried several different recommendations
> for adjusting the TCP receive window size. None of them,
> including those directly from Microsoft, seem to have any
> impact. I'm capturing my own traffic and my advertised window
> is always in th
Well, "theory" says that the receive window size is based on how much memory
a host has. If it has very little memory, then it has to make sure the other
side doesn't send too much data without giving the host breathing time to
flush its buffer, write to disk, and ACK. So a host has to advertise a
s vermill wrote:
>
> s vermill wrote:
> >
> > Group:
> >
> > On a W2k machine, I've tried several different recommendations
> > for adjusting the TCP receive window size. None of them,
> > including those directly from Microsoft, seem to have any
> > impact. I'm capturing my own traffic and my
> An interesting side note: Ethereal apparently doesn't support window
> scaling.
Do you mean the tcp window scale option or just the phenomenon of having
data outstanding? You can always just count un-acked bytes for an idea
of how big the window is. It's dyanmic, of course, and don't forget
> So one wild idea would be to remove memory from the host. Or maybe you
could
> get it to use up a chunk of memory by opening lots of large docs and/or
> using a RAM disk!?
In practice, you'd have to really restrict the amount of RAM to a level
that the OS wouldn't function. You're talking about
To all,
There is a freeware program called Dr. TCP Win for Windows 2000/XP that
allows you to change both the MTU and TCP Window size--requires a reboot,
though, after the change.
Cheers!
--
Richard A. Deal
Visit my home page at http://home.cfl.rr.com/dealgroup/
Author of Cisco PIX Firewalls,
16 matches
Mail list logo