We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now


Windows 2000 DC/Fileserver slow every 2 weeks

Medium Priority
Last Modified: 2013-11-09
Windows Server 2000 - File server, DC, SQL 2000 on one box

When users modify .doc files and press "save" it takes 10 to 20 seconds to save changes. If I reboot the server they can save instantly with no delay but then 14 days later it starts slowing down again.

This box also has an instance of sql server 2000 running on it. Memory is configed at a set level for sql. This server was also upgraded from NT40 to Win2K. There is only one box and it is the DC, SQL server and File server. Any ideas why a reboot fixes it yet 2 weeks later it's at a crawl again?

Watch Question

Sr. Server Administrator

1) Temporarily disable any real-time anti-virus software to see if that helps, and if it does, re-configure your AV settings to something more appropriate for your environment.  Also, in cases of a direct cross-over cable between a client and a server, buy a switch and use regular CAT 6cable.

2) Verify that you are running the latest and the correct network adapter driver.   Obtain and install the latest anufacturer driver for the card instead of using one that Microsoft has provided.  (also see if the manufacturer has any utilities you can use to check NIC performance).

3) Verify that you can resolve the server name from the client and that theclient can resolve the server.  Check DNS and make sure your server has only the correct IP address.

4) Verify the network cards of all clients and servers, switches, hubs and routers are set to the same speed and duplex settings (i.e. 100mb/sec & Full duplex).  If the hubs or switches have utilities you could use to see if it
may be logging errors that will help your troubleshoot if it is a patch cable somewhere on the network

5) The problem may be SMB signing or LAN Manager authentication level.  InWindows 2003, default server policy forces all SMB traffic to be digitally signed which seems to cause a problem in some configurations of XP Pro.  In
Local Security Policy (Start > Run > secpol.msc > OK) navigate to security options (Security settings > Local policies > Security) and try disabling the option for Microsoft network server:digitally sign communications(always).  Ensure you do this on all machines involved (such as via a GPO for an OU).  Run gpupdate /force on the server after making the change and do the same on the client machine afterwards.

Security settings that can cause a problem with downlevel client access:

See also:
Slow SMB performance when you copy files from Windows XP to a Windows 2000 domain controller:

http://support.microsoft.com?kbid=822219 "You Experience Slow File Server Performance and Delays Occur When You Work With Files That Are Located on a File Server "

6) Another possibility involving slowness between  XP and Windows Server 2003 computers:

New registry entry for controlling the TCP Acknowledgment (ACK) behavior in
Windows XP and in Windows Server 2003:

7..Try this ...
 Slow File Write from Windows 2000 to Windows NT 4.0 Server

8.Slow Network Performance Occurs If You Copy Files to a Windows 2000 <http://kb/article.asp?id=Q321098

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
dlonganDirector of IT

I have seen this with my own server environment, but each scenerio is different.
Depending on your enviroment, it could be numrous things

1.  network card
2.  network hub/switch port
3.  network cabling
4.  network hub/switch and network interface card incompatiblites
5.  network interface card drivers
6.  capture network traffic during the slow done

Here are couple of kb articles from ms:


How much memory is being shown as available at the time of slow down (check in Task Manager).  Things that are resolved by a reboot that then  recur after a while can sometimes be traced to an application not releasing memory.  This is called a memory leak and can cause repeatable slow downs after time.


Thanks guys. Memory and all other resources look fine. I opened up perfmon and watch disk IO and other counters and there's no bottleneck or spikes when users try to save changes.

I'm curious as to why this is not apparent after reboot and then after 2 weeks it's so slow. Is there something that happens perhaps network related that can cause these issues wo worsen over time?
Hi mate

Had a look around and saw this article.


Are you running the latest SP for the OS and the SQL Server?



Thanks everyone. It's definately a networking issue. It turns out that I traced back a couple of the drops in their area and found that someone had spliced a couple of phones into the cat5 cables to save money from putting in phone lines to the switch room.

The setup was OK when they were on a 10MB connection but now they have a GB switch and it's reared it's ugly head.

Points awarded for putting me in the right direction. Thanks!
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.