DCDIAG

  • Thread starter Thread starter Penny
  • Start date Start date
P

Penny

I'm trying to run a test on my DC and am hearing about tools like DCDIAG.
I'm running windows 2000 server SP4 and these don't seem to be installed.
Where would I get these tools?

The reason I'm wanting to check the health of my dc is because ever since I
took DHCP off the firewall appliance and installed it on the dc, performance
on my PC has degraded. What used to work instantly now takes sometimes
upwards of a minute to accomplish.

Windows explorer takes a full minute to open, I think it's hanging on my
mapped network drives. I've disconnected them and reconnected them with no
gains in performance. Another example is when I remote desktop into the DC
it too takes a lot longer than it did before I made the DHCP change.

I'm almost positive the lags I'm seeing has something to do with my changes,
but I'm not sure how to go about troubleshooting what the problem is.
 
Hello Penny,

On the 2000 server install disk open tools\supoort and run support.msi. This
will install the complete tools.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
 
I do this weekly via a script but here you go

Run diagnostics against your Active Directory domain.

If you don't have the support tools installed, install them from your server
install disk.
d:\support\tools\setup.exe

Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
-> dnslint /ad /s "ip address of your dc"

**Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
in the forest. If you have significant numbers of DC's this test could
generate significant detail and take a long time. You also want to take
into account slow links to dc's will also add to the testing time.

If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests
without having to learn all the switch options. The details will be output
in notepad text files that pop up automagically.

The script is located on my website at
http://www.pbbergs.com/windows/downloads.htm

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

When complete search for fail, error and warning messages.

Description and download for dnslint
http://support.microsoft.com/kb/321045


--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
 
In
Penny said:
I'm trying to run a test on my DC and am hearing about tools like
DCDIAG. I'm running windows 2000 server SP4 and these don't seem to
be installed. Where would I get these tools?

The reason I'm wanting to check the health of my dc is because ever
since I took DHCP off the firewall appliance and installed it on the
dc, performance on my PC has degraded. What used to work instantly
now takes sometimes upwards of a minute to accomplish.

Windows explorer takes a full minute to open, I think it's hanging on
my mapped network drives. I've disconnected them and reconnected
them with no gains in performance. Another example is when I remote
desktop into the DC it too takes a lot longer than it did before I
made the DHCP change.

I'm almost positive the lags I'm seeing has something to do with my
changes, but I'm not sure how to go about troubleshooting what the
problem is.
Click to expand...

The problems you are describing are indicative of a DNS mis-config. If the
ISP's DNS, or even the router's IP address is in ip properties of any
machine (DC, member servers or clients), numerous problems such as slow
logons, failure to authenticate accessing printers, mapping drives, etc.
ONLY the internal DNS must be in IP properties of all domain machines.

Also what can cause this is a multihomed DC (more than one NIC) . This is
problematic. Another thing is a single label AD DNS domain name ("mycompany"
instead of "mycompany.com," "mycompany.net", etc).

A "dcdiag /v" will help find errors. Once it finds them, they must be
translated and diagnosed, which the tool doesn't do. If you can post any
errors that show up in the dcdiag results, as well as an unedite ipconfig
/all, that will help begin a diagnosis.


--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Infinite Diversities in Infinite Combinations
 
Back
Top