Vista is not optimised by default. The commands to enable the next generation IP stack features are: netsh interface tcp set global ecncapability=enabled netsh interface tcp set global congestionprovider=ctcp Please add this important info. to your Vista FAQ!

2007-09-21 15:39:32

Please read http://en.wikipedia.org/wiki/Windows_Vista_networking_technologies

2008-03-30 10:01:07 (Vonbrown )

DrTCP does indeed work. As previously stated it will allow you to select from all your different network interface devices. I do not reccomend changing the MTU.

2009-05-11 12:56:26 (uh60james )

Bunk! Routers that don't know about ECN can still drop packets normally, but there is some ECN-hostile network equipment on the Internet. For this reason, ECN is disabled. Compound TCP is a modified TCP congestion avoidance algorithm, meant to improve networking performance in all applications. It is not enabled by default in the pre-Service Pack 1 version of Windows Vista, but enabled in SP1 and Windows Server 2008. It uses a different algorithm to modify the congestion window - borrowing from TCP Vegas and TCP New Reno. For every acknowledgement received, it increases the congestion window more aggressively, thus reaching the peak throughput much faster, increasing overall throughput. Install SP1 for Vista.

2008-06-10 14:36:18 (Irish Shark )

I beg to differ about drtcp not supported with vista,I tried the app.and changed the tcp recieve window values to various settings and each one had an effect! I used suggested tweak settings from dslreports.com after providing my info. needed to see if my settings were adjustable even after reading that vista tcp stack settings were optimized at default values,(255500 being default)and setting the value to 65535.So I would suggest ONLY tweaking tcp receive window settings.(I might need to add that I had a choice between ethernet and wifi card sett. on a laptop,I was using the ethernet for an isdn provider.) from: snowdude4570@yahoo.com

2008-12-15 07:17:18

I get Element not found

2008-01-14 18:22:40 (james579 )

get message that .dll helper cannot be loaded is there a fix for this.

2007-11-01 21:35:51 (louis666 )

When I try to do this my vista says "the operation requires elevation"? :O

2007-11-01 19:50:37

The following .dll helper cannot be loaded iA109a-k13-3zxd-bape-TE Is there a fix for this.

2007-11-15 20:55:54 (cmharmon )

You need to run cmd as Administrator.......

2007-12-27 12:49:17 (wgn_peace )

I mistakenly entered "Local Area Connection" and got device not found. I then tried "Wireless Network Connection" and got an ok. Thanks-

2010-11-21 20:45:25 (redschmed )

Element not found means check your connection type you entered.

2010-11-21 20:46:57 (redschmed )

I have ran this comand and the result was a message "elevation is required". I was in admin login. What can i do?

2008-01-08 09:28:12

If you get element not found your not specifying the right subinterface (i.e. network connection). If you are using a wireless connection, use netsh interface ipv4 set subinterface "Wireless Network Connection" mtu=xxxx store=persistent

2008-08-26 01:28:16 (Steven_M )

Right click on the command prompt and select RUN AS ADMINISTRATOR

2008-04-30 12:28:47 (Irish Shark )

It worked fine for me, but maybe because I didn't know what I was supposed to do. I went into the Control Panel, opened Administrative Tools, opened System Configuration, Tools, Command Prompt & entered the informtion as instructed, then did it again changing the xxxx to 1500 so it actually worked.

2008-07-11 20:06:54 (WGBlasdel )

Hello. I have a question. I entered the command exactly as it is listed above and got an Ok back but the MTU did not change. Am I supposed to put the "" around Local Area Network in this command? Thanks for your help!

2009-03-06 07:34:52 (AceDSL )

all i get when i type this in is "element not found"

2009-06-01 13:25:23

if you receive "element not found" / try running the following from an elevated cmd window less quotes: "netsh interface ipv4 show subinterfaces" look to the lower right of those results under "Interface" and be sure that you are typing the exactly as shown with quotes. For instance, my Interface had actually been re-named "Local Area Connection 2" because I had previously uninstalled my network card. Worked fine after adding the 2. Good Luck

2011-05-12 22:04:51

Thank you, worked fine and big help. This solved an issue with a Win7 box and slow CIFS shares to a ReadyNAS (dropping MTU frmo 1500 to 1470 in this case)

2011-10-08 21:23:38