slug slow XP network response - a Solution!

[Bruce Waldie]

Oh, OK, By NEW, I assumed that it meant that it was new to XP and already
there. Neither the message or the article said that I had to CREATE the
key, they only said that it was NEW.

The typos I accept, I make lots of them myself. I was just pointing it out
for the sake of accuracy.

Thanks for the message. I will be able to try the results out tonight. I
made the new entry early this am and rebooted server 2003, but was not able
to test it due to a broken water main out front. (Winter is hard).

Bruce Waldie, P.Ag.
PhotoComp Systems Inc.

Thanks for the input, but I cannot find any such key. Your example
seems to be incorrect, in that the key should be:

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\PARAMETERS\InterfaceS\[GI
D

(that is, it is missing the PARAMETERS subkey and misses the S on
Interfaces)

That's just a typo by Juerg.

And even the knowledgebase article 328890 has it wrong. It gives it
as:

HKLM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\[GID

(That is, it is missing the SYSTEM subkey) Hardly promotes
confidence in the solution.

You are correct, the KB article misses \SYSTEM\ but that's just
another typo.

No matter, I cannot find such a TcpAckFrequency key anywhere in the
registry on my Server 2003 machine. The kb article indicates that
such a key should exist, and that its default is even 2. What is
going on here?

No, read the SUMMARY section, it states (my emphasis):

TcpAckFrequency is a _NEW_ registry entry...

you have to add it; if it doesn't exist XP behaves as if it is set to
2.

HTH

Regards,

Parish

Bruce Waldie




(e-mail address removed) (Juerg Thoeny) wrote in

Hi

The problem can be solved by setting the DWORD TcpAckFrequency to 1
in the registry:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Interface\[GID of your
Network Interface}\ You have to change this on your server and it
works only after reboot.

There is also a Microsoft article which describes this:
http://support.microsoft.com/default.aspx?kbid=328890


Kind regards

Juerg

 

[Guest]

hi,

disable the "weblcient" servcie on your xp clients.
This will fix your problems