Naming information cannot be located because...

[Rogerio Destito]

No Authority could be contacted for authentication .

Thats the error message I got while triyng to open AD
Users and Computers Snap In on a DC for a domain .

That box, due to a infra structure problem, was down for
48 hours and from my understanding, lost syncronism with
domain.

This domain has a second DC that is running fine .
System State restore from backup tape is possible.

What is the best approach to fix that ?

Using DCPROMO to remove box from AD and then reinsert is
an option ?
Rds

 

[Matjaz Ladava [MVP]]

48 hours offline should not break synchronization. the problem is somewhere
else. See that your Dc can speak to DNS server as it probably has problem
locating Dc's on the network. run dcdiag to get more info on your error

dcpromo is an option, but it will probably fail and you will end up using
dcpromo /forceremoval which will then force you to manualy clean up metadata
in AD (http://support.microsoft.com/?kbid=216498) after that you can promote
server again to DC

--
Regards

Matjaz Ladava
MVP Windows Server - Directory Services
(e-mail address removed), (e-mail address removed)

 

[Rogerio Destito]

DCDIAG executed and got the following error:

* Connecting to directory service on server <ServerName>.
[<ServerName>] LDAP bind failed with error 31.
A device attached to the system is not functioning.

Executed also :

netdom reset <ComputerName> /domain:<DomainName>,

But the answer was :

There are currently no logon servers available to serve
the logon request .

But NLTEST shows 2 DCs :
VMS-SAO-S01 (PDC - problem box)
VMS-SAO-S02 (Second DC - OK)

Any clue ?