Domain comtroller crashed

From: Nasser (kwalikw_at_hotmail.com)
Date: 05/18/04


Date: Tue, 18 May 2004 02:41:07 -0700

OK. I setup a new DC, lets call it DC1, and istablished a
new tree. then remotely over frame relay, I set up another
domain controller, lets call it DC2. DC1 crashed and I
lost everything. DC2 is still operational with the
messages about not finding DC1 for replication. Now I
installed windows 2000 server again on DC1. during the
configuration of active directory on DC1 I selected DC1 as
a secondary DC and entered the domain name. everything
went fine. Id like to mention that before I set up active
directory, I was told that I should enter the ip of DC2 as
the DNS and Gateway for DC1, otherwise the active
directory setup was not gonna work. so now I keep getting
a message in the system log "The account-identifier
allocator failed to initialize properly. The record data
contains the NT error code that caused the failure.
Windows 2000 will retry the initialization until it
succeeds; until that time, account creation will be denied
on this Domain Controller. Please look for other SAM
event logs that may indicate the exact reason for the
failure." so now I can't add any new user or delete any
user. sure there is lots more than that, but for now Im
trying to solve this problem. I could use a hand.
Thanks



Relevant Pages

  • Re: Domain Mess - Problem promoting second server to DC
    ... >>> Our windows 2003 server domain controller for NAME.Local was ... >>> the AD that was now running on DC2. ... >>> I have been able to rebuild the DC1 machine and join it as a member ... >>> I installed DNS on DC2, and configured DC2 to use itself for DNS. ...
    (microsoft.public.windows.server.dns)
  • Re: additional 2003 domain controller
    ... I have added an 2nd domain controller to a 2003 domain. ... DC1 ... On both domain controllers I can see the Active directory information ... longer able to view/edit active directory on DC2. ...
    (microsoft.public.windows.server.active_directory)
  • Re: NTFRS Event ID: 13568 , plz help resolveing of this issue - UR
    ... I have tried to install additional domain controller on another ... My aim was to move the FSMO roles to DC2 so that I would remove DC1 ... mind that our 64 Bit Windows server would become domain controller. ...
    (microsoft.public.windows.server.active_directory)
  • Domain Mess - Problem promoting second server to DC
    ... Our windows 2003 server domain controller for NAME.Local was the only ... I was able to bring up a second domain controller on an old PC (DC2) to ... but DC1 died before I was able to gracefully demote ... I installed DNS on DC2, and configured DC2 to use itself for DNS. ...
    (microsoft.public.windows.server.dns)
  • Re: Replacing 2003 Domain Controller
    ... Let's call the existing server DC1. ... Bring up the new server simultaneously and name it DC2. ... I currently have a domain controller with DNS and WINS also ...
    (microsoft.public.windows.server.general)