How Can I Repair my AD ?

  • Thread starter Thread starter Átila Einstein
  • Start date Start date
Á

Á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
 
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
 
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
 
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
 
Back
Top