Ponthecomputer
asked on
Windows 2000 DC/Fileserver slow every 2 weeks
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
ASKER
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?
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.
https://www.experts-exchange.com/questions/20694611/MS-SQL-2000-Standard-Database-slow-down-only-remedied-by-server-reboot.html
Are you running the latest SP for the OS and the SQL Server?
Rob
Had a look around and saw this article.
https://www.experts-exchange.com/questions/20694611/MS-SQL-2000-Standard-Database-slow-down-only-remedied-by-server-reboot.html
Are you running the latest SP for the OS and the SQL Server?
Rob
ASKER
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!
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!
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:
http://support.microsoft.com/kb/822219/en-us
http://support.microsoft.com/kb/169789/en-us