http://support.microsoft.com/default...uct=winsvr2003
Which talks about a dword parameter called TcpAckFrequency in Win 2003
server. This default is '2', I had to add the value in to my registry and
change the value to '1' then reboot the server. Once I did this,
performance increase was so extreme, it actually ran like a server should.
Yesterday with that flag set to 2 (default), it took 2 minutes and 10
seconds to copy a 1.1mb folder of 121 files from the server to another
directory on the same server. With the value at 1, it did the same folder
in under 5 seconds. This is why I've been pulling my hair out so much since
performance over the network was so shitty.
Highlights of the Q article:
------------------------------
Warning If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk.
Subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interf
aces\<Interface GUID>
Entry: TcpAckFrequency
Value Type: REG_DWORD, number
Valid Range: 0-255
Default: 2
Description: Specifies the number of ACKs that will be outstanding before
the delayed ACK timer is ignored. Microsoft does not recommend changing the
default value without careful study of the environment. For more
information, visit the following Microsoft Web page:
http://www.microsoft.com/technet/pro...on129121120120
If you set the value to 1, every packet is acknowledged immediately because
there is only one outstanding TCP ACK as a segment is just received. The
value of 0 (zero) is not valid and is treated as the default, 2. The only
time the ACK number is 0 is when a segment is not received and the host is
not going to acknowledge the data.
------------------------------
Now one interesting point is that there is another Q article
(
http://support.microsoft.com/default...0&Product=wins
vr2003) that says if you add the value and change it to 1, you still may
not notice a difference. It talks of a hotfix first required before 2003
will recognize the change (the file tcpip.sys is in this hotfix). I read a
few other messages about this change and some people did not have to first
call MS PSS to get the fix, the server did recognize the change. In our
case, I thought what the hell, I have nothing to lose if it doesn't work,
then I'll call PSS. Fortunately, it did work without this hotfix.
This is such an exciting day for me!!!
"TheSingingCat" <(E-Mail Removed)> wrote in message
news:40cdd25a$1_1@news....
> Hi gents,
>
> I've got a very perplexing problem here that's been nagging me for the
last
> two weeks. We have recently deployed a new sever in our domain and
promoted
> it to a PDC (it was NT4.0) From that point, we did an inplace upgrade to
> 2003 Server Standard running in Interim Mode. Our remaining 4 servers are
> still NT4.0 and two of those are BDCs.
>
> My problem is that when data is written to the 2003 Server (HP Proliant
> ML370 G3) it takes an incredible amount of time even for the smallest of
> folders. I'll give you an example.. from an XP workstation, we copy a
300kb
> folder with about 30 files (pretty small yes?) it takes about 90seconds.
> The folder is being copied from the ML370 to a different directory on the
> same server. If from the same client, I copy the same folder from the
2003
> server to one of our NT4.0 BDCs, the copy process is *very* fast (maybe
> 3seconds), I have through other tests ruled out network infrastructure.
>
> If we copy the same folder from the client workstation (xp) to the ML370
> server, it takes about the same amount of time (90seconds). Copying it
off
> the server to the client is FAST (3seconds).
>
> Now the strange part: We had a few NT4.0 and 98 machines kicking around
> still, when we copy the folder from those guys, it is FAST.
>
> Local drive access on the server is also extremely quick. It seems so far
> that only writes from 2000 and XP clients are affected. We had an even
> older machine running 95 with the AD support pack installed, it is slow.
>
> I've tried updating the SmartArray 532 firmware, network drivers, new
> network card, smartstart v7.0 and same problem persists. Server reports
no
> errors or configuration problems either within the event log or the hp
diag
> tools. This server is our primary DNS server, we have a Secondary DNS
> server that is NT4.0, all lookups etc. seem to be fine.
>
> I've literally spent 2 weeks isolating the problem and am now convinced it
> is only 2000 / XP workstation Write speeds to the 2003 server that is
being
> affected, I just can't figure out why or how to resolve. Clients report
no
> screwball messages except for Autoenrollment errors since presumably my
DNS
> isn't fully AD integrated yet. For humor sake, I've disabled
> autoenrollment on a few clients to test but that didn't help...
>
> Any ideas?
>
> Thank you.
>
>
>
Similar Threads
Linear Mode
