2000 DC has died.... but HELP it was an operations master

[spectrum48k]

Hi All,

This is my story so far…. HELP!

My 2000 Server - Primary Domain controller died, due to a disk failure. I luckily had a full backup of the system state. It was the operation master!

I have another DC in the domain which is also 2000 Server. This server is also setup to be a global catalog. I don’t seem to be able to take over as operation master as this server is now offline.

The problem I now have is My original Primary DC has been rebuilt with 2003 server, I don’t seem to be able to find the 2000 server disk and serial… the old admin lost it! So I was wondering is there any way I can safely have my 2000 Server take over the FSMO roles and become the new operation mastering. I don’t much feel like rebuilding the entire domain.

Can any body help? here's the logs from ntdsutil and dcdiag on the Secondary DC.

ntdsutil: domain management
domain management: connections
Connected to DC2 using credentials of locally logged on user
server connections: quit
domain management: select operation target
select operation target: list roles for connected server
Server "DC2" knows about 5 roles
Schema - CN=NTDS Settings,CN=DEADDC,CN=Servers,CN=Default-First-Site,CN=Sit
es,CN=Configuration,DC=DOMAIN,DC=domain-group,DC=co,DC=uk
Domain - CN=NTDS Settings,CN= DEADDC,CN=Servers,CN=Default-First-Site,CN=Sit
es,CN=Configuration,DC=DOMAIN,DC=domain-group,DC=co,DC=uk
PDC - CN=NTDS Settings,CN= DEADDC,CN=Servers,CN=Default-First-Site,CN=Sites,
CN=Configuration,DC=DOMAIN,DC=domain-group,DC=co,DC=uk
RID - CN=NTDS Settings,CN= DEADDC,CN=Servers,CN=Default-First-Site,CN=Sites,
CN=Configuration,DC=DOMAIN,DC=domain-group,DC=co,DC=uk
Infrastructure - CN=NTDS Settings,CN= DEADDC,CN=Servers,CN=Default-First-Sit
e,CN=Sites,CN=Configuration,DC=DOMAIN,DC=domain-group,DC=co,DC=uk



J:\>dcdiag

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site\DC2
Starting test: Connectivity
......................... DC2 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site\DC2
Starting test: Replications
[Replications Check,DC2] A recent replication attempt failed:
From DEADDC to DC2
Naming Context: CN=Schema,CN=Configuration,DC=Domain,DC=Domain,DC=co,DC=uk
The replication generated an error (1722):
Win32 Error 1722
The failure occurred at 2008-01-17 12:52.39.
The last success occurred at 2008-01-15 09:51.57.
51 failures have occurred since the last success.
[DEADDC] DsBind() failed with error 1722,
Win32 Error 1722.
The source remains down. Please check the machine.
[Replications Check,DC2] A recent replication attempt failed:
From DEADDC to DC2
Naming Context: CN=Configuration,DC=DOMAIN,DC=Domain-Domain,D
C=co,DC=uk
The replication generated an error (1722):
Win32 Error 1722
The failure occurred at 2008-01-17 12:52.17.
The last success occurred at 2008-01-15 09:57.59.
51 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,DC2] A recent replication attempt failed:
From DEADDC to DC2
Naming Context: DC=DOMAIN,DC=Domain,DC=co,DC=uk
The replication generated an error (1722):
Win32 Error 1722
The failure occurred at 2008-01-17 12:51.56.
The last success occurred at 2008-01-15 09:58.29.
51 failures have occurred since the last success.
The source remains down. Please check the machine.
......................... DC2 passed test Replications
Starting test: NCSecDesc
......................... DC2 passed test NCSecDesc
Starting test: NetLogons
......................... DC2 passed test NetLogons
Starting test: Advertising
......................... DC2 passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: DEADDC is the Schema Owner, but is not responding to DS R
PC Bind.
[DEADDC] LDAP connection failed with error 58,
Win32 Error 58.
Warning: DEADDC is the Schema Owner, but is not responding to LDAP
Bind.
Warning: DEADDC is the Domain Owner, but is not responding to DS R
PC Bind.
Warning: DEADDC is the Domain Owner, but is not responding to LDAP
Bind.
Warning: DEADDC is the PDC Owner, but is not responding to DS RPC
Bind.
Warning: DEADDC is the PDC Owner, but is not responding to LDAP Bi
nd.
Warning: DEADDC is the Rid Owner, but is not responding to DS RPC
Bind.
Warning: DEADDC is the Rid Owner, but is not responding to LDAP Bi
nd.
Warning: DEADDC is the Infrastructure Update Owner, but is not res
ponding to DS RPC Bind.
Warning: DEADDC is the Infrastructure Update Owner, but is not res
ponding to LDAP Bind.
......................... DC2 failed test KnowsOfRoleHolders
Starting test: RidManager
[DC2] DsBindWithCred() failed with error 1722. Win32 Error 1722

......................... DC2 failed test RidManager
Starting test: MachineAccount
......................... DC2 passed test MachineAccount
Starting test: Services
......................... DC2 passed test Services
Starting test: ObjectsReplicated
......................... DC2 passed test ObjectsReplicated
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... DC2 passed test frssysvol
Starting test: kccevent
......................... DC2 passed test kccevent
Starting test: systemlog
......................... DC2 passed test systemlog

Running enterprise tests on : DOMAIN.Domain.co.uk
Starting test: Intersite
......................... DOMAIN.Domain.co.uk passed test
Intersite
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.Domain.co.uk failed test
FsmoCheck

 

[jfwebber]

You will have to seize the role(s) that were being held on the dead DC. Take a look at this and it will get you started.

http://support.microsoft.com/kb/255504

Jim W MCSE CCNA
Network Manager