DCDIAG problem

  • Thread starter Thread starter Michael
  • Start date Start date
M

Michael

When trying to run dcdiag on our workstations to test our domain
controllers - we get the message that the GUI DNS name cannot be resolved to
an IP address - It also states that the DNS Server is not responding to
Directory Service requests. This happens on both DC's.

Any ideas as to why this could be happening.

Thanks

Spikey

--
 
In
Michael said:
When trying to run dcdiag on our workstations to test our domain
controllers - we get the message that the GUI DNS name cannot be
resolved to an IP address - It also states that the DNS Server is not
responding to Directory Service requests. This happens on both DC's.

Any ideas as to why this could be happening.

Thanks

Spikey
Click to expand...

Running dcdiag from a workstation you have to add the either the server or
domain name switch. dcdiag s:/servername or dcdiag n:/domainname

Make sure all clients and servers are only pointing to your local DNS server
which is usually you DC for DNS. No ISP'S DNS allowed.
Run netdiag /test:dns /v on the DC to verify DNS registration.
 
The DCDIAG now seems to be working OK - On the PDC however, it fails the
systemlog test with a series of error events - Event ID 0xC000003d - Event
string could not be retrieved
TMISVR failed test systemlog.

On the second DC - it states the browser service has failed to retrieve the
systemlog.

Any ideas what is causing this problem.


Kevin D. Goodknecht said:
Running dcdiag from a workstation you have to add the either the server or
domain name switch. dcdiag s:/servername or dcdiag n:/domainname
news:[email protected]...
Click to expand...
 
In
Michael Hewson said:
The DCDIAG now seems to be working OK - On the PDC however, it fails
the systemlog test with a series of error events - Event ID
0xC000003d - Event string could not be retrieved
TMISVR failed test systemlog.

On the second DC - it states the browser service has failed to
retrieve the systemlog.

Any ideas what is causing this problem.
Click to expand...

I would have to see the errors from the event log to have any idea what is
causing your problem.
It may be a DNS problem, improper DNS configuration will cause many errors.
If you will post the error from the event log, an ipconfig /all I can get a
better idea.
 
I decided to reboot both DC's and then rerun DCDIAG - The errors have all
disappeared and all seems to be OK.

Thanks for your help
Cheers
Michael Hewson (MCP)
 
Back
Top