How to Troubleshoot Slow DC/GC Peformance?

Discussion in 'Active Directory' started by Steve, Jun 8, 2004.

  1. Steve

    Steve Guest

    I've got 3 DC/GC in my single domain AD forest. All are located on my LAN
    which consists of approx. 75 workstations. I've also got a WAN of 10
    locations over T1 or DSL with approx. 200 workstations which these boxes

    1 DC is a PIII 600 with 512MB RAM and it is also the DHCP server, DNS, WINS
    server and it also hosts the primary FSMO roles (IM, PDCE, etc). The 2nd DC
    is the same HW, but also hosts NAV sig files for the domain. The 3rd DC is
    a PIII 1GHz with 512MB RAM which also has RAS services.

    The issue is that the DC with the primary FSMO roles is very speedy. If I'm
    in AD users and computers, properties for objects come up very quickly...2-3
    seconds. The other 2 DC's are quite slow..the one with NAV sigs on it can
    take up to 30 secs to show object properties if I switch to it from AD users
    and computers. The 3rd DC can take approx. 15 seconds.

    How can I determine why this is?


    Steve, Jun 8, 2004
    1. Advertisements

  2. Steve

    Steve Guest

    I'll check the NTDS counters to see what might be obvious. Memory,
    CPU and disk usage seems OK. It spikes at times, but no counter is
    Steve, Jun 8, 2004
    1. Advertisements

  3. Steve

    Steve Guest

    Any recommendation for which counters to run..there are counters a plenty
    for NTDS.

    I'm seeing performance issues with Outlook 2003 and am trying to eliminate
    the GC's as a culprit, but this slow performance for AD users and computers
    is pointing to them since I know how dependant OL is to the GC's.

    These DC's are pointing to the internal DC for DNS. I've looked in the DS
    event log and there are just info logs 700/701, 200/202 messages relating to
    online defrag.

    Aside from OL other network delays.


    specifically, the Directory Services log. I wouldn't expect to see machines
    of that spec being slow.
    but this sounds like a DNS/ Site locator problem. The event logs are the
    best place to start. I'd also check things with dcdiag /v /c /e and netdiag
    Steve, Jun 8, 2004
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.