n Wed, 21 Apr 2004 19:08:31 +1200, Enkidu < XXXX@XXXXX.COM >
I already considered the idea of putting in a temporary server but I
can't even get machines to join the domain, much less become a domain
controller! The output from DCDIAG is not promising...
Starting test: Connectivity
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly registered
Starting test: FsmoCheck
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
......................... DOMAIN.com failed test FsmoCheck
There are also failures to register the RR in DNS, and MS's tech notes
that apply to that symptom are not relevant. And I'm getting Event
1202s every five minutes, "Security policies are propagated with
warning. 0x4b8 : An extended error has occurred." And once again,
MS's tech note (re Power Users) is not applicable.
As a last resort I'm going to take a stab at rebuilding the domain
database (in SYSVOL?) to see if that brings the domain back to life,
but the fact that MetaEdit's "check" function turned up so many
inconsistencies in the metabase, and the fact that NTFRS also needed
to be reset (was getting "The File Replication Service has detected
that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in
JRNL_WRAP_ERROR"), makes me doubt it's worth the effort to invest much
more time in cleaning up the mess on this box.