HELP: Slow Domain Controller (Win2000)
I installed Windows 2000 Advanced Server on a pentium IV 2.66 GHZ with 256MB of RAM, and a 40GB hard disk.
I installed DNS after I was sure that Windows 2000 A.S. is working properly, without any errors. It installed properly.
Then I setup a Domain Controller on this system, added users, and everything was OK.
After I added the first computer to the domain, the DC reported some errors with DNS. I checked Event Viewer regularly and understood that those errors related to autoupdating of forward lookup zones. Thus I put a message here in Experts Exchange, and learnt how to solve that problem. By now, no error messages apear in Event Viewer. But a big problem has happened:
From the moment I added computers to the domain, when I log off the DC and leave it for about 30min, and on the other side, users are logging in and off, my DC starts to be so slow. I usually log in on my DC within a 30 seconds period (maximum), but this way it takes at least 2 minutes. When I want to open Active Directory of Members and Computers, it takes some time, and when it is open, and I double click an item, the property page does not open. I can not close AD window thence, as it says "close all proprty pages before closing the window" while the propery page is not open yet.
When I restart this server, it will be OK for some 30min period, and after that, the problem happens again.
I am sure that no viruses infected this computer. As much as I understand, such problems relate to DNS problems, since the server repeats some lookup tasks and slows down, but I am sure that my DNS is working OK.
Any ideas? I need possible causes to be checked.
My other computers run Windows 2000 Professional.
Thanks in advance
Huji
I installed DNS after I was sure that Windows 2000 A.S. is working properly, without any errors. It installed properly.
Then I setup a Domain Controller on this system, added users, and everything was OK.
After I added the first computer to the domain, the DC reported some errors with DNS. I checked Event Viewer regularly and understood that those errors related to autoupdating of forward lookup zones. Thus I put a message here in Experts Exchange, and learnt how to solve that problem. By now, no error messages apear in Event Viewer. But a big problem has happened:
From the moment I added computers to the domain, when I log off the DC and leave it for about 30min, and on the other side, users are logging in and off, my DC starts to be so slow. I usually log in on my DC within a 30 seconds period (maximum), but this way it takes at least 2 minutes. When I want to open Active Directory of Members and Computers, it takes some time, and when it is open, and I double click an item, the property page does not open. I can not close AD window thence, as it says "close all proprty pages before closing the window" while the propery page is not open yet.
When I restart this server, it will be OK for some 30min period, and after that, the problem happens again.
I am sure that no viruses infected this computer. As much as I understand, such problems relate to DNS problems, since the server repeats some lookup tasks and slows down, but I am sure that my DNS is working OK.
Any ideas? I need possible causes to be checked.
My other computers run Windows 2000 Professional.
Thanks in advance
Huji
DNS by itself is a real memory hungry..If this is a DC I would definitely add more memory. You can confirm this by launching Perfmon and watching performance counters for memory or disk caching.
ASKER
Ok
I'll do it as soon as possible which will be saturday. I will put a message after I carried on what you advised.
Thanks for now
Keep in touch
Huji
I'll do it as soon as possible which will be saturday. I will put a message after I carried on what you advised.
Thanks for now
Keep in touch
Huji
Wil stay tuned.. MSGeek Note on weekend less load on the server.
ASKER
Sorry for being late.
1)Look at this picture for details on what my server does when being slow:
http://ssrc.tums.ac.ir/TaskManager.gif
I don't know what "lsass" is, but it is using a lot of memory and CPU resources! (This may not be the cause of the problem, of course.)
2)My server is busy from Saturday to Wednesday, and not on Thursdays and Friydays.
Wish you can help me
Huji
1)Look at this picture for details on what my server does when being slow:
http://ssrc.tums.ac.ir/TaskManager.gif
I don't know what "lsass" is, but it is using a lot of memory and CPU resources! (This may not be the cause of the problem, of course.)
2)My server is busy from Saturday to Wednesday, and not on Thursdays and Friydays.
Wish you can help me
Huji
lsass is the Local Security Authority Service, it is what authenticates users for the WinLogon service.
Perhaps this will help : http://support.microsoft.com/default.aspx?scid=kb;EN-US;311127 or if you a re running SMS (which I believe you are not) http://support.microsoft.com/default.aspx?scid=kb;EN-US;311127
Perhaps this will help : http://support.microsoft.com/default.aspx?scid=kb;EN-US;311127 or if you a re running SMS (which I believe you are not) http://support.microsoft.com/default.aspx?scid=kb;EN-US;311127
ASKER
Well, I installed SP1 to SP4 and the issue is solved.
I split the points between the people who paied attention to this question, only for their attention.
Good luck!
Huji
I split the points between the people who paied attention to this question, only for their attention.
Good luck!
Huji
Not necessary (Ireally don't want a grade of C anyway) I will ask for a refund for you. MSGeek
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks a lot MSGeek
And thank you too, Netminder
Huji
And thank you too, Netminder
Huji
I don't get paid unless the server is responding.. :-)
Watch closely the processes that are consuming memory - what you're looking for is a process that steadily climbs in the amount of memory it is using. When you determine this post the process for us.
If no process is "leaking" then you might have a DNS issue - but let's look at one thing at a time.