From: Ellen K. 

The network at my company is already a snail, guess if/when they start
adding Vista boxes that will finish it off.

On Sun, 24 Dec 2006 15:18:50 -0500, "Rich Gauszka"
 wrote in message :

>
>"Geo"  wrote in message
news:458ec873$1{at}w3.nls.net...
>> Ok, so I was doing a test just now and best transfer rate I could get over
>> gigE was 9mb/s.
>>
>> I'm about to tweak some settings per the below but if anyone has any other
>> suggestions I would appreciate it.
>>
>> Geo.
>>
>>
>> Windows XP/2000 Server/Server 2003
>> The magical location for TCP settings in the registry editor is
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
>>
>> We need to add a registry DWORD named TcpWindowSize, and enter a
>> sufficiently large size. 131400 (make sure you click on 'decimal') should
>> be
>> enough. Tcp1323Opts should be set to 3. This enables both rfc1323 scaling
>> and timestamps.
>>
>>
>
>It appears MS took away tuning parameters - Obviously a DRM function as to
>limit bandwidth and thus stop piracy 
>
>http://www.networkperformancedaily.com/2006/12/vistas_tcpip_promises_and_peri.
html
>Enabling or disabling CTCP or auto-window sizing are not, as they were in
>Windows XP, configurable from the registry - CTCP can be enabled/disabled
>from the command prompt but there has been no mention of tuning parameters
>which leads us to ask the question: How are you supposed to configure this
>setting in Vista? (Microsoft Employees: Please give us a comment if you
>know!) Our next steps are to get some boxes powerful enough to run Vista,
>get the time to do it and start looking at it for ourselves.
>
>For companies with manually tuned network environments (with high-bandwidth
>and high-latency - such as satellite links) it should do a better job than
>window scaling alone, but the fact that it's dynamic and self-tuning means
>you've lost control over it - that's a scary position for a sysadmin.
>

--- BBBS/NT v4.01 Flag-5