Question : Active Directory Users and Computers VERY SLOW

Hi there,

I have a few WIndows 2003 servers, one is an exchange server, one is a member server. Recently, Active Directory Users and Computers has become ridiculously slow. It starts up fast enough, but when I right click on a person to view their Properties, it'll sit for 30 seconds or more, and then the page will come up.

Doesn't matter if I do it on the Exchange server or the member server. If I bring up one user's properties, quickly close it, and then bring up another user, it comes up nice and fast like it used to. But if I put a minute or two between Property pages, it just lags for that 30 seconds each time.

I'm in the process of adding about 90 new students to my Active Directory schema and at the current rate it's going to take me hours and hours. I have no idea why it's suddenly slowed down, but in all fairness I haven't really been doing much to our users over the summer time when the kids were not in school.

Exchange server is running DNS, member server is not, both have an internal and external NIC. Member server is running routing and remote access for our VPN. Note that we also have a Windows 2000 server running, which was the "original" server in this farm. It is currently being phased out, however it is still part of the network, had Exchange server on it once apon a time, now only acts as a file server and backup DNS. It is still part of AD. Not sure if that would have anything to do with it.

Any suggestions on what I can try to fix it?

Answer : Active Directory Users and Computers VERY SLOW

is the NS1 computer your gateway computer for the internal network?

I would remove the ISP DNS from the external card...it doesn't need it.  The external NIC should only have IP/subnetmask/gateway.  The internal NIC should have an IP/subntemask/NO gateway/INTERNAL DNS.

On the win2k box open DNS MMC in administrative tools.  Right click on the servername, properties.  what is listed under forwarders?  it should only have your ISP's DNS server or an upstream corporate DNS server if one exists.

Restart the NS1 after making the changes and test.