DCDIag error on Windows 2003 Server SP2
DCdiag gives the following error :
Starting test: Connectivity
The host 8e363e9d-1508-4f2a-b038-dc1054dc177b._msdcs.appsoft.accord.com could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name (8e363e9d-1508-4f2a-b038-dc1054dc177b._msdcs.appsoft.accord.com) couldn't be resolved, the server name (blaze.appsoft.accord.com) resolved to the IP address (192.168.1.69) and was pingable. Check that the IP address is registered correctly with the DNS server.
I have followed almost all replies and reviews on this. But I was not able to resolve this issue. Any help would be appreciated.
Re: DCDIag error on Windows 2003 Server SP2
Dcdiag.exe tool analyzes the state of domain controllers in a forest or enterprise and reports any problems to assist in troubleshooting. Dcdiag encapsulates detailed knowledge of how to identify abnormal behavior in the system. So the above error is related to your DNS settings. Refer http://support.microsoft.com/kb/825036 for assistance on the same.
|Tags: dcdiag, error code, ip address, service pack 2, windows 2003 server|
|Thread Tools||Search this Thread|
|Similar Threads for: "DCDIag error on Windows 2003 Server SP2"|
|Thread||Thread Starter||Forum||Replies||Last Post|
|Cannot locate Global Catalog server error 1355 from dcdiag||lopa||Small Business Server||2||15-09-2009 07:46 PM|
|0xc00002e1 error on Windows 2003 server||CheckMeNot||Operating Systems||3||13-12-2008 05:19 PM|
|Permissions error - Windows Server 2003 R2||Mike||Windows Server Help||3||23-09-2008 10:42 PM|
|MMC 3.0 user snap-in error (windows server 2003, exchange server 2||RonnyEhv1982||Windows Server Help||1||15-03-2008 12:15 AM|
|How to fix DCDIAG errors on windows server||Robbin M||Active Directory||1||22-03-2007 06:35 PM|