Unfortunately disabling TCP
Auto-Tuning causes Server 08 to force a window size of 64K (which is what it’s
at currently). For some reason, it won’t scale beyond 64K. As far as a I know
there isn’t a way to force a higher window size. What I can’t figure out is
why it isn’t scaling any higher automatically.
From:
wireshark-users-bounces@xxxxxxxxxxxxx
[mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Frank Bulk
Sent: Thursday, September 04, 2008 11:50 PM
To: wireshark-users@xxxxxxxxxxxxx
Subject: Re: [Wireshark-users] TCP Window Sizes
Perhaps you should just turn off auto-tuning?
http://www.speedguide.net/read_articles.php?id=2574
Regards,
Frank
From:
wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx]
On Behalf Of Aaron Allen
Sent: Thursday, September 04, 2008 9:13 AM
To: 'wireshark-users@xxxxxxxxxxxxx'
Subject: [Wireshark-users] TCP Window Sizes
This is primarily a TCP related question, so if there is a more
appropriate forum for this question, please point me in the right direction.
I am trying to identify the source of a slowdown for an
upload to Amazon S3 from a Windows 2008 server. Packet captures seem to
indicate the problem is with the TCP window size. When I manually
increase the TCP window size on another machine, I am easily able to get
maximum bandwidth utilization. But, for some reason, this 2008 machine
won’t increase the window size beyond 64K.
I can’t increase the TCP Window size on the 2008 machine
because of the new and “improved” auto tcp tuning. Is there something
else I should be looking for that could be causing the window size to not be
scaled any higher?
