Re: Updates
- From: kpg <no@xxxxxxxx>
- Date: Mon, 11 Jun 2007 07:10:31 -0700
I did this on one of the 2k3 sp2 the servers:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"Tcp1323Opts"=dword:00000000
That disables timestamps and window scaling, and as a result
forces the max tcp window size to 64k.
On the Vista machine: (from the admin prompt)
netsh interface tcp set global autotuning=disabled.
This turns off Receive Window Auto-Tuning, and prevents vista
from adjusting its tcp window size.
Rebooted Vista but not the server, and the network was still
slow (but only when communicating with the two 2k3 sp2 servers).
Come in this AM and voila - every thing works fine. hmmmmmmm.
OK. I can rule out the server setting (I think) because there
are 2 servers, both exhibited the problem and now both work
fine. I only disabled 1323 on one of them.
I can rule out the Vista autotuning because a reboot Friday
would work just a well as a reboot today...(unless the server
keeps tcp connection info for a time...nah)
If I were ambitious, I would undo my changes and see what
that does, but alas...
My initial assumption was that upgrading [sic] to svr 2k3 sp2
caused the problem, and I further assumed that Vista was at
fault. The sp2 introduced some new tcp capabilities, and Vista
supports the new tcp capabilities, so a problem there could
result in the behavior I saw, poor communication between Vista
and the 2k3 sp2 machines. NIC hardware and driver incompati-
bilities with the "new capabilities" are an equally likely
culprit.
So why the delayed auto-fix?
kp "that's a rhetorical question" g
.
- Follow-Ups:
- Re: Updates
- From: Michael D. Alligood [CertGuard]
- Re: Updates
- References:
- Vista still sucks
- From: kpg
- Vista still sucks
- Prev by Date: Re: Vista still sucks
- Next by Date: Re: Vista still sucks
- Previous by thread: Re: Vista still sucks
- Next by thread: Re: Updates
- Index(es):
Relevant Pages
|