Receive Window Auto-Tuning on Vista.

Soci blog » Blog Archive » Receive Window Auto-Tuning Vist??ban

Soci blog » Blog Archive » Receive Window Auto-Tuning Vist??ban — Fri, 06 Jul 2007 13:03:05 GMT

PingBack from http://soci.hu/blog/index.php/2007/07/06/receive-window-auto-tuning-vistaban/

re: Receive Window Auto-Tuning on Vista.

Sooner Al [MVP] — Mon, 09 Jul 2007 13:54:21 GMT

The first link to KB932170 is broken. Here is the correct link...

http://support.microsoft.com/kb/932170

re: Receive Window Auto-Tuning on Vista.

Christopher Blanc — Wed, 25 Jul 2007 22:58:23 GMT

Thank you -- these comments have saved us from some prolonged Windows Vista copy experiences. Another thing that seemed to help was avoiding ZIP archives, which seem to delay coming into Vista machines, but not as much when being copied from said machines.

Access 2007 design view performance on Windows Vista vs Windows XP

Tonys Microsoft Access Blog — Fri, 27 Jul 2007 02:42:44 GMT

A very interesting thread brought out some interesting differences in the networking stack in Windows

re: Receive Window Auto-Tuning on Vista.

Jorge Eduardo — Fri, 17 Aug 2007 09:01:50 GMT

Autotuninglevel must be disabled for Ibackup otherwise you get a blue screen of death. The problem is you need to remember to disable this manually from command prompt every time you boot.

re: Receive Window Auto-Tuning on Vista.

wndpteam — Fri, 17 Aug 2007 18:29:34 GMT

Jorge:

I would not expect that the autotunning level is related to Backup. If you have a few momements, would you so the following:

*Open up "Problem Reports and Solutions"

*Click on "View Problem History"

*Find the blue screen entry and double click it

*Scroll down and find the BucketID and let us know what it is?

Thanks

-- Ari

re: Receive Window Auto-Tuning on Vista.

George Schizas — Mon, 27 Aug 2007 18:26:26 GMT

After reading about it on Microsoft's public newsgroups, it seems that setting "AutoTuningLevel=normal" or generally something other than disabled, causes Windows Live Messenger to NOT connect, producing the error 0x81000306, which seems to be a plague these days! So, if anyone receives this error, they could just type (as admin) "netsh int tcp set global autotuninglevel=disabled" to fix Messenger!

It depends on the NAT device and it's firmware. I would suggest "netsh interface tcp set global autotunninglevel=restricted" before a complete disable as the post tries to explain. -- Ari

re: Receive Window Auto-Tuning on Vista.

Tim Wilde — Mon, 27 Aug 2007 20:29:34 GMT

I've experienced and find many postings in the Vista Community that some PCs running Vista seem to be forced to use the Public Location settings, Local access only, which causes them to be unable to connect to a LAN or the Internet. By adding a static local ip address, gateway address, DNS addresses, etc. to the Alternate IP Address settings for TPC v4 these PCs are able to connect fine. I wonder if window scaling is causing these Vista PCs to be unable to work with some router's DHCP function?

"Local Access Only" is a sign that the machines are either not receieving a DHCP response, or that with the settings recieved they are unable to access beyond the local router. Public Location is the default location until a user selects an option that tells Vista that the network is a private one (Home or Work). DHCP runs in parallel to TCP instead of ontop of TCP, so TCP Window Scaling should not affect it. -- Ari

re: Receive Window Auto-Tuning on Vista.

Dean — Thu, 30 Aug 2007 03:42:54 GMT

So Windows Scaling is supposed to also be in Windows 2000, Windows 2003 and XP. So why didn't those products feel the effects of routers that didn't support scaling ? Also, since it seems that a lot of routers don't support this ( even though the RFC has been around since 1992 ) is it even worth turning on untill all hardware supports it.

Do the main routers on the Internet support it ?

The Cable Guy January 2007 article attempts to explain the difference.-- Ari

Wiring the house for a Home Network - Part 5 - Gigabit Throughput and Vista

ASPInsiders — Sat, 01 Dec 2007 09:59:52 GMT

I posted earlier about copying files across my new Gigabit home network . I was getting about 10 MB/s

Wiring the house for a Home Network - Part 5 - Gigabit Throughput and Vista

Scott Hanselman's Computer Zen — Sat, 01 Dec 2007 11:41:43 GMT

re: Receive Window Auto-Tuning on Vista.

Jorge Schrauwen — Sat, 05 Jan 2008 20:16:26 GMT

There is a typo in the blog!

its not "autotunninglevel" but "autotuninglevel"!

[Fixed. Thanks -Ari]

re: Receive Window Auto-Tuning on Vista.

MarkDubya — Wed, 27 Feb 2008 01:49:42 GMT

How 'bout find and replace all "tunning" with "tuning"

Sure. -- Ari

re: Receive Window Auto-Tuning on Vista.

Mike — Fri, 14 Mar 2008 00:39:14 GMT

Sections of this article sounds hauntingly familiar:

http://lwn.net/Articles/92727/

re: Receive Window Auto-Tuning on Vista.

iain — Fri, 18 Apr 2008 14:18:04 GMT

tried this and received this error...found the same on two vista machines:

"Set global command failed on IPv4 The requested operation requires elevation"

Yes, this is a change to the underlying OS settings and requires you to run as administrator. Open a cmd shell by Right Click -> Run as administrator. Depending on your account type you either need to approve or type in the an administrator account password. Once the administrator cmd shell is open, you can use the netsh cmds

-- Ari

re: Receive Window Auto-Tuning on Vista.

Cecil Ward — Tue, 06 May 2008 21:23:56 GMT

Could Microsoft do more to help get this issue resolved. Suggestions: post a list of broken routers w. firmware versions; have a campaign to reach out to router mfrs to get firmware updates ready; ship a small tool that definitively tests for the issue on a vista client machine.

re: Receive Window Auto-Tuning on Vista.

Radoslav Petrik — Tue, 03 Jun 2008 19:45:51 GMT

Are you kidding? How could possibly Microsoft test all the network devices on the market (not even talking about firmware versions)? There are millions of them.

It is not their responsibility to make sure that network equipment vendors do their job correctly.

And as written in the article, Microsoft does offer a tool it is called Internet Connectivity Evaluation Tool and can be freely downloaded from their website.

I bet if they were shipping it with Vista, they would get an antitrust law suit from European Union or somebody.

Links for Wednesday 17 June 2008

Richard's Rant — Wed, 18 Jun 2008 07:06:41 GMT

Well, after a few months of quiet, I am back. Interesting article about Models and Specifications 4 ways

re: Receive Window Auto-Tuning on Vista.

Petter Nilsen — Mon, 30 Jun 2008 10:22:29 GMT

It's interesting that IE 7+ seems to set "autotuninglevel=restricted" programmatically on Vista, as other browser vendors have been forced to do as well. If there is a reliable way to only do this if required due to buggy routers, it would be useful to know about how.

Well the mechanism is WSAIoctl SIO_SET_COMPATIBILITY_MODE with WsaBehaviorAutoTuning option. I believe Vista SP1 introduced some general mechanisms to reduce autotuning when it sees slow connections with small window sizes for sockets that do not set that option. Even with that, it's still a reactive test, the user still has to experience the bad network behavior before the stack can attempt to adapt to it.

re: Receive Window Auto-Tuning on Vista.

Michael L. Croswell — Thu, 03 Jul 2008 02:27:49 GMT

Is there a netsh.dll so that this could be called programmatically (as opposed to using ShellExecute or CreateProcess)?

Also, will this be fixed in Vista? Wouldn't it make sense (!) if the OS had just set this to Restricted or Disabled by default. Or perhaps, like DirectX, there would be a way to set it without going to a command-line program?

We've done work in SP1 to lessen the impact for users with problematic network devices. We've heard general feedback about the lack of more programatic access to network settings and enjoy getting more information about specific scenarios that are intresting to our customers. I'd also like to point out one more type of control of the AutoTunning setting, Group Policy. gpedit.msc -> Computer Configuration -> Windows Settings -> Policy Based QoS -> Right Click: Advanced Qos Settings -> Inbound TCP Traffic is a set of levels that map 0 -> diabled, 1 -> highlyrestricted, 2-> restricted and 3 -> normal. This allows bulk deployment of the settings in a domain.

-- Ari

re: Receive Window Auto-Tuning on Vista.

Mark Wall — Mon, 14 Jul 2008 14:12:43 GMT

Whats the difference between "RWND Auto-Tuning" and "Window Scaling Option"(RFC 1323)?

Does Auto-Tuning adjust the max. RWND (or the scaling factor) while the connection is already established?

How does this work technically?

Or does "Auto-Tuning" just mean that "Window Scaling Option" is used per-connection (while it is established) and not globally for all connections?

Mark

VISTA file transfer blues..

adamsalah — Fri, 25 Jul 2008 01:26:38 GMT

So I decided to reorganize my laptop running VISTA ultimate. First things first, make room on the system...

re: Receive Window Auto-Tuning on Vista.

Cecil Ward — Fri, 21 Nov 2008 22:51:43 GMT

18 months on, there are still major router manufacturers who have yet to release fixes to their firmware to resolve window scaling issues.

Microsoft could help its customers by (i) liaising with manufacturers to exert some gentle pressure, and (ii) also publicising those who do the right thing and reminding the rest of how they are missing out on the benefits of getting listed amongst the righteoud and acquiring a "logo".

Suggestion. What about a patch for vista that adds a new 'split' pair of two 'subnet-vs-global' autotuning parameters to control the behavior independently wrt subnet-local vs external ip addresses? That would allow users on a fast LAN to benefit without problems caused by routers or bad servers out on the internet.

re: Receive Window Auto-Tuning on Vista.

R Sherwood — Tue, 17 Mar 2009 19:43:47 GMT

So, is there a QoS policy that may be applied to set the autotuninglevel on Vista? Or is this only set through netsh? And, I believe the change to be persistent when set through netsh - is this the case?

An existing connection was forcibly closed by the remote host

The Windows Directors' Cuts — Thu, 04 Jun 2009 12:22:38 GMT

An existing connection was forcibly closed by the remote host