DCDIAG Result : AD01 is responding to directory service requests

Thenkung
Thenkung used Ask the Experts™
on
Please consideration error message (dcdiag) below , How to action this case

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.AD01>dcdiag

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\AD01
      Starting test: Connectivity
         The host 48c71090-27b0-458c-9d84-e1677eb810dc._msdcs.domain.co.th c
ould not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name
         (48c71090-27b0-458c-9d84-e1677eb810dc._msdcs.domain.co.th)
         couldn't be resolved, the server name (AD01.domain.co.th)
         resolved to the IP address (X.X.X.X) and was pingable.  Check that
         the IP address is registered correctly with the DNS server.
         ......................... AD01 failed test Connectivity


Doing primary tests

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

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
The host 48c71090-27b0-458c-9d84-e1677eb810dc._msdcs.domain.co.th c
ould not be resolved to an IP address


Logs Clearly shows that there is an issue with DNS misconfiguration. I would suggest you to restart the netlogon service on the DC by goint to services.msc . Once done , On the DC Run

Ipconfig /registerDns.

You can go ahead and run Netdiag /fix on the DC , so that All the Generice records of a DC will get register on the DNS

Also make sure on the DC,

 Correct Primary and secondary DNS IP address are present TCP/IP properties of it. Disable unused NIC on the DC

Refer below discussion

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Q_27447647.html

Regards,

_Prashant_
Krzysztof PytkoSenior Active Directory Engineer
Top Expert 2012
Commented:
Did you change IP address of that DC last time ?

Log on there and in command-line type

ipconfig /flushdns
ipconfig /registerdns
dcdiag /fix

and please provide the output of

dcdiag /e /c /v >c:\dcdiag.log

Regards,
Krzysztof
Commented:
The GUID 48c71090-27b0-458c-9d84-e1677eb810dc._msdcs.domain.co.th can't be resolved may be due to the DC is been deleted or missing CNAME records.

Restart the DNS server, Netlogon services. Also, run ipconfig /flushdns and ipconfig /registerdns to refresh the missing records. Also run dcdiag /fix as well as netdiag /fix.
http://blogs.msdn.com/b/mskumar/archive/2007/10/22/create-and-verify-dns-srv-and-a-records-for-client-automatic-client-sign-in.aspx

Note: Netdiag is deprecated in widows 2008 & above.
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
Thank you for all recommend.I will follow by your information and inform result of operation soon. Best Regard.

Author

Commented:
Thank you for help.
Krzysztof PytkoSenior Active Directory Engineer
Top Expert 2012

Commented:
You're welcome :)

Krzysztof

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial