How Can I Repair my AD ?

[Átila Einstein]

I Try use DCDIAG.EXE but ocurr err: " The Procedure entry point
DsIsMangledDnW could not be located in the dynamic link library NTDSAPI.dll.

Help me..

Thanks...

Átila

 

[Jimmy Andersson [MVP]]

Try this report tool:
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd915706/MPSRPT_DirSvc.EXE

Regards,
/Jimmy

 

[Johan Arwidmark]

It looks like you have the wrong version of dcdiag (the error
indicates that)

Download the latest from
http://www.microsoft.com/windows2000/techinfo/reskit/tools/new/dcdiag-o.asp

If it still fails, run it on a Windows XP SP1 client (in the domain)

regards

Johan Arwidmark

Windows User Group - Nordic
http://wug.lutteman.se

 

[Atila]

Dear Jimmy,

I run DCDIAG and this software response : " cancel all tests because
didn´t conect 689ae150-dce3-449c-a467-a61617c50c76.msdcs.mydomain.com.br.
Verify DNS, DHCP, Name Server.....

How Can I Make ? Reinstalll my DNS ? Where is the Problem ?

Help me...

Thanks

Átila Einstein

 

[Jimmy Andersson [MVP]]

Did you run MPS Report?

Regards,
/Jimmy
--
Jimmy Andersson, Q Advice AB
Microsoft MVP - Active Directory
---------- www.qadvice.com ----------

 

[Atila]

Yes Jimmy.
This Tools write a lot of reports... and now ?

????

Átila Einstein

 

[Átila Einstein]

Dear Jimmy..
This is result of the DCDIAG /A


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SERVIDOR10
Starting test: Connectivity
689ae150-dce3-449c-a467-a61617c50c76._msdcs.empresa.com.br's server
GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(689ae150-dce3-449c-a467-a61617c50c76._msdcs.empresa.com.br)
couldn't

be resolved, the server name (servidor10.empresa.com.br) resolved
to the

IP address (200.111.111.111) and was pingable. Check that the IP

address is registered correctly with the DNS server.
......................... SERVIDOR10 failed test Connectivity

Doing primary tests

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

Running enterprise tests on : empresa.com.br
Starting test: Intersite
......................... empresa.com.br passed test Intersite
Starting test: FsmoCheck
......................... empresa.com.br passed test FsmoCheck

-----------------------------------------

Átila Eisntein

 

[Átila Einstein]

Dear Johan,
This is result of the DCDIAG /A


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SERVIDOR10
Starting test: Connectivity
689ae150-dce3-449c-a467-a61617c50c76._msdcs.empresa.com.br's server
GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(689ae150-dce3-449c-a467-a61617c50c76._msdcs.empresa.com.br)
couldn't

be resolved, the server name (servidor10.empresa.com.br) resolved
to the

IP address (200.111.111.111) and was pingable. Check that the IP

address is registered correctly with the DNS server.
......................... SERVIDOR10 failed test Connectivity

Doing primary tests

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

Running enterprise tests on : empresa.com.br
Starting test: Intersite
......................... empresa.com.br passed test Intersite
Starting test: FsmoCheck
......................... empresa.com.br passed test FsmoCheck