dcdiag utility

  • Thread starter Thread starter Bob
  • Start date Start date
B

Bob

Greetings,

I recently ungraded our network (4,500 users) from
winNT4.0 to single win2000 Active Directory domain (its
using DNS, DHCP, WINS). The upgrade went well and
everything has been running smoothly for a couple of
months.

I decided to run the dcdiag utility to check for problems
with Active Directory. Below is the complete error
message is generated in the logfile upon running the
command:

dcdiag /s:SV52 /v /f:c:\logfile \c

The host ?% could not be resolved to a valid IP address.
Check the DNS server, DHCP, server name, etc
.......................... SV52 failed test

All the DC are setup in DNS with a static IP address and
correct forward/reverse records. Nslookup show a correct
responce for each.

The q313108 (Dcdiag Incorrectly Reports an Unsuccessful
Connectivity Test for Some IP Addresses) article list the
known problem and suggest the latest SP and hotfixes. All
the DC are at the latest service pack level and are fully
patched.

I wouldn't be worried about this to much, but I'm
preparing for an Exchange 5.5 to Exchange 2000 migration
in the near future and would like to have the AD directory
service fully functional.

Any ideas on how to fix the problem would be great.



dcdiag logfile
#########################################
Domain Controller Diagnosis

Performing initial setup:
* Connecting to directory service on server SV52.
* Collecting site info.
* Identifying all servers.
* Found 3 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SV52
Starting test: Connectivity
* Active Directory LDAP Services Check
The host ?% could not be resolved to a valid IP
address.
Check the DNS server, DHCP, server name, etc
......................... SV52 failed test
Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SV52
Skipping all tests, because server SV52 is
not responding to directory service requests

Running enterprise tests on : dept.company.com
Starting test: Intersite
Skipping site Default-First-Site-Name, this site
is outside the scope provided by the

command line arguments provided.
......................... dept.company.com passed
test Intersite
Starting test: FsmoCheck
GC Name: \\sv52.dept.company.com
Locator Flags: 0xe00001fc
PDC Name: \\SV01.dept.company.com
Locator Flags: 0xe00001fd
Time Server Name: \\sv52.dept.company.com
Locator Flags: 0xe00001fc
Preferred Time Server Name:
\\sv52.dept.company.com
Locator Flags: 0xe00001fc
KDC Name: \\sv52.dept.company.com
Locator Flags: 0xe00001fc
......................... dept.company.com passed
test FsmoCheck
 
Bob,

This is a known issue with the CD version of DCDIAG. It is resolved in the
latest service pack:

313108 Dcdiag Incorrectly Reports an Unsuccessful Connectivity Test for
Some IP
http://support.microsoft.com/?id=313108

Steve Dodson [MSFT]
Directory Services
--------------------
Content-Class: urn:content-classes:message
From: "Bob" <[email protected]>
Sender: "Bob" <[email protected]>
Subject: dcdiag utility
Date: Tue, 30 Sep 2003 14:22:52 -0700
Lines: 90
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Thread-Index: AcOHmQHIIdHcs5HEQt2sPP2FTD9p/A==
Newsgroups: microsoft.public.win2000.active_directory
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.win2000.active_directory:49935
NNTP-Posting-Host: TK2MSFTNGXA08 10.40.1.160
X-Tomcat-NG: microsoft.public.win2000.active_directory


Greetings,

I recently ungraded our network (4,500 users) from
winNT4.0 to single win2000 Active Directory domain (its
using DNS, DHCP, WINS). The upgrade went well and
everything has been running smoothly for a couple of
months.

I decided to run the dcdiag utility to check for problems
with Active Directory. Below is the complete error
message is generated in the logfile upon running the
command:

dcdiag /s:SV52 /v /f:c:\logfile \c

The host ?% could not be resolved to a valid IP address.
Check the DNS server, DHCP, server name, etc
......................... SV52 failed test

All the DC are setup in DNS with a static IP address and
correct forward/reverse records. Nslookup show a correct
responce for each.

The q313108 (Dcdiag Incorrectly Reports an Unsuccessful
Connectivity Test for Some IP Addresses) article list the
known problem and suggest the latest SP and hotfixes. All
the DC are at the latest service pack level and are fully
patched.

I wouldn't be worried about this to much, but I'm
preparing for an Exchange 5.5 to Exchange 2000 migration
in the near future and would like to have the AD directory
service fully functional.

Any ideas on how to fix the problem would be great.



dcdiag logfile
#########################################
Domain Controller Diagnosis

Performing initial setup:
* Connecting to directory service on server SV52.
* Collecting site info.
* Identifying all servers.
* Found 3 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SV52
Starting test: Connectivity
* Active Directory LDAP Services Check
The host ?% could not be resolved to a valid IP
address.
Check the DNS server, DHCP, server name, etc
......................... SV52 failed test
Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SV52
Skipping all tests, because server SV52 is
not responding to directory service requests

Running enterprise tests on : dept.company.com
Starting test: Intersite
Skipping site Default-First-Site-Name, this site
is outside the scope provided by the

command line arguments provided.
......................... dept.company.com passed
test Intersite
Starting test: FsmoCheck
GC Name: \\sv52.dept.company.com
Locator Flags: 0xe00001fc
PDC Name: \\SV01.dept.company.com
Locator Flags: 0xe00001fd
Time Server Name: \\sv52.dept.company.com
Locator Flags: 0xe00001fc
Preferred Time Server Name:
\\sv52.dept.company.com
Locator Flags: 0xe00001fc
KDC Name: \\sv52.dept.company.com
Locator Flags: 0xe00001fc
......................... dept.company.com passed
test FsmoCheck
Click to expand...


--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
Back
Top