Our forums are currently in maintenance mode and the ability to post is disabled. We will be back up and running as soon as possible. Thanks for your patience!

General discussion


Domain Controller Diagnosis

By mob_dream ·
First of all I would like the TechRepublic and every one inside this name for all the efforts.

and I have a problem in my DC that after echcking logs and reading mesages desc. I did the dcdiag test and I got the Following:

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\DC01
Starting test: Connectivity
The host coul
d not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
( couldn't
be resolved, the server name (dc01.mob_dream) resolved to the IP
address ( and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... DC01 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DC01
Skipping all tests, because server DC01 is
not responding to directory service requests
and all other tests passed. Also my Exhange server giving my some errors and I think all coz of Domain Controller. could any one please help with that
thank you

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by HAL 9000 Moderator In reply to Domain Controller Diagnos ...

What is allocating the DHCP address here?

It should be the Domain Controller and if this isn't setup on that you'll have all sorts of problems establishing connections in the Domain.


Collapse -

by lowlands In reply to Domain Controller Diagnos ...

looks like your DC's are not properly registered in DNS.
Log on to one of your DC's and open a command window. Then run "netdiag /fix".

This will populate your DNS again with all AD related entries.

Collapse -

by curlergirl In reply to Domain Controller Diagnos ...

Also, all of your servers should have STATIC IP addresses, not DHCP-assigned. If this is not the case, this could be the source of your problem - if the domain controller gets a new dynamic IP address, then it is not being registered in DNS appropriately. There are a number of reasons this can happen - but it's not really important. The important thing is to be sure your servers (including your Exchange server, even if it is not a DC) have static IP addresses.

Hope this helps!

Collapse -

by mob_dream In reply to Domain Controller Diagnos ...

Thank you so much everyone I try then all..

Collapse -

by p.j.hutchison In reply to Domain Controller Diagnos ...

On the DNS Windows server, enable 'Register this connection's address in DNS' on the DNS tab of TCPIP Properties the LAN connection then type:
ipconfig /registerdns.

This should create the SRV records on the DNS server needed for AD.

Related Discussions

Related Forums