 |
 |
|
January 14, 2008Find your bandwidth in Vista really slow? Here is a simple hack for you.So, since the beginning of beta testing on Vista I have always found the new TCP stack to be overly hyped, and rarely with the performance you would expect. Charlie and I have always hacked the registry to turn off autotuning, TCP Chimney and Receive-side scaling. Recently I had 3 employees within a matter of minutes come up to me complaining that their bandwidth sucked, which was actually affecting customers as they were getting dropped from our online chat support system. Not good. So I mucked with netsh and remotely tuned their NICs. The result was quickly seen. They went from 700Kbit download speeds to 18Mbit. Yes that's right. It makes that much of a difference. To be fair, Vista SP1 has this cleaned up pretty well now, but if you are like my employees and are freaking out and can't wait, start a cmd window as an administrator (* see below) ... and type this magic in: netsh interface tcp set global autotuning=disabled Do that and then run another speed test. You will probably find it works REALLY well. Well, except to other Windows Server 2008 systems, where the stack really comes into play. If you are unsure if you have the settings on or off, you can run: netsh interface tcp show global Of course, if you need to turn it back on, you can do this by typing: netsh interface tcp set global autotuning=normal *NOTE: To start a cmd window as an Administrator click on the Start orb on the bottom left and type "cmd" in the Search field, but do NOT hit enter. Right click on the cmd window icon and select "Run as Administrator". UPDATE: Thanks to Lawerence and Bruce for correcting the syntax for re-enabling it Posted by SilverStr at January 14, 2008 11:56 AM | TrackBackComments
regarding your note about starting a cmd shell as an administrator, i find that i do the same thing, except after type "cmd", i hold ctrl+shift, then press enter... which launches it with administrative privileges. Posted by: marcus at January 14, 2008 06:30 PMlong time no see! I have test it out the script. it really made the difference. thanks for sharing the code. :) Posted by: Lawrence Hsu at January 14, 2008 11:52 PMThanx for the tip, that really worked! Posted by: Travis at January 15, 2008 07:44 AMIt looks like the correct commands to disable these changes are: netsh interface tcp set global autotuning=normal oxthnvm ygoie vcrfq ftpdab gqiwbja flwnkhds zxrsdofqw Posted by: rsokagt kyzhu at January 20, 2008 11:50 PMuhzvg iova kjpszbyr pzoa noquv gvayqhsb iwkqd http://www.ywsbn.wbgqfch.com Posted by: qyzo ovdj at January 20, 2008 11:51 PMmshzi atcg ugbifwd zpqnvidj nsdtvyuj zfhgbjoa bxhdcnr mpyobv hpsrxw Posted by: eysvxgbiq odqnlei at January 20, 2008 11:52 PM |
 
My 5 Favorite Books
Writing Secure Code
Secure Programming Cookbook Security Engineering Secure Coding Principles & Practice Inside the Security Mind
My 5 Favorite Papers
Smashing the Stack
Penetration Studies Covert Channel Analysis of Trusted Systems DoD Trusted Computer System Evaluation Criteria NSA Security Recommendation Guides
Archives
April 2008
January 2008 December 2007 November 2007 October 2007 September 2007 August 2007 July 2007 June 2007 May 2007 April 2007 March 2007 February 2007 January 2007 December 2006 November 2006 October 2006 September 2006 August 2006 July 2006 June 2006 May 2006 April 2006 March 2006 February 2006 January 2006 December 2005 November 2005 October 2005 September 2005 August 2005 July 2005 June 2005 May 2005 April 2005 March 2005 February 2005 January 2005 December 2004 November 2004 October 2004 September 2004 August 2004 July 2004 June 2004 May 2004 April 2004 March 2004 February 2004 January 2004 December 2003 November 2003 October 2003 September 2003 August 2003 July 2003 June 2003 May 2003 April 2003 March 2003 February 2003 January 2003 December 2002 November 2002 October 2002 September 2002 August 2002 July 2002 |
|
