Server problem

  • Thread starter Thread starter Phil Sigley
  • Start date Start date
P

Phil Sigley

Hi im appealing for help with a problem we have,

The we have a 2 domain controllers on our network running windows 2000
server. These have active directory on them for the computer accounts etc.
The server is the main domain controller has died so now nobody can log on
to the network, the other server says the user accounts are still held in
active directory. Unfortunatly the backups havent been working and thats
what i was fixing when the disk in the main DC died so ive had to install a
fresh copy of 2 k server on this machine. Is there a way i can get back to
how was without starting again.

Phil Sigley
 
To have the second DC take over you need to make sure you either transfer or
seize the FSMO roles the first DC held. Depending on if you are going to
bring the first DC back or not will determine if you seize or transfer the
roles.
See:
Using Ntdsutil.exe to Seize or Transfer FSMO Roles to a Domain Controller

http://support.microsoft.com/default.aspx?scid=kb;en-us;255504

HOW TO: View and Transfer FSMO Roles in the Graphical User Interface

http://support.microsoft.com/default.aspx?scid=kb;en-us;255690

Flexible Single Master Operation Transfer and Seizure Process

http://support.microsoft.com/default.aspx?scid=kb;en-us;223787

FSMO Placement and Optimization on Windows 2000 Domain Controllers

http://support.microsoft.com/default.aspx?scid=kb;en-us;223346





You need to set the second DC as a Global catalog.

See:

How to: Create or Move a Global Catalog in Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;313994





And you need to make sure you have DNS set up properly. If you had you DNS
as AD integrated you would have all the DNS info on the second DC and you
would just have to point the users to the new DNS server.

See:

How to: Configure DNS for Internet Access In Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675





If the first DC was a DHCP server you will need to recreate that also.





hth

DDS W 2k MVP MCSE
 
If you have a 2nd DC then all you have to do is Seize all FSMO roles and do
a metadata cleanup. You will probally have to change the IP address to that
of the failed DC so that the clients can find a DNS server. After this has
been done you can promote the failed rebuilt server to DC. Change the Ip
address back after you install DNS on the server and move FSMO roles back.
Follow these links to accomplish the task.

Using Ntdsutil.exe to Seize or Transfer FSMO Roles to a Domain Controller
http://support.microsoft.com/default.aspx?scid=kb;en-us;255504

HOW TO: Remove Data in Active Directory After an Unsuccessful Domain
Controller Demotion
http://support.microsoft.com/default.aspx?scid=kb;EN-US;216498

HTH

Paul McGuire
 
Thanks very much, i seized the roles using ntdsutil, did the metadata
cleanup and took the old server out of sites and services and gave the
existing DC the IP address of the old server and everyinthing is now fine.

Cheers again

Phil Sigley
 
Back
Top