Need to setup another DC on existing AD

  • Thread starter Thread starter Chris Donahue
  • Start date Start date
C

Chris Donahue

I have an existing PDC on an AD domain. I wanted to add
another DC so I may remove the old one. Upon adding the
new DC, I experienced several error and was never able to
replicate the two servers. Now I want to remove AD from
the new DC but it gives me errors saying that it can't.
Any help on how to remove this from DC and also any
information on how to properly add a new DC to an existing
AD domain. Thanks for all your future help.
 
I have tried to run the metadata cleanup, but when I get
to the part where I select site number, it says that no
site are listed and I can go no further. Thanks for the
reply, Also I am getting an error stating that there is a
dupicate name on the network. I have run nbtstat -RR and -
n, there are three separate entries, how do I remove them??
 
What does your server show as the domain name? I suspect that you may have
what is called a disjointed DNS namespace and that would cause you to have
these type of issues. You domain name needs to be in the form of
"something.something". So a host on your network would have a computer name
of "host.something.something" as it's FQDN. I suspect your domai name is
"something" if so there is no fix for this without a little work. If this is
the case reply here and I'll give some options.

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

scrockel@***No_SPAM***hotmail.com
 
My computer name is mdtitle2.48-dom-mdtitle. The domain
name is 48-dom-mdtitle. I really need to get this fixed,
and all you information is very much appreciated. Thanks.
 
Are you in Native mode? Do you have any NT4 BDC's? You seem to have the
disjointed DNS namespace and this is not an easy fix. What you bascially
need to do IF you are in mixed mode is to either use an existing NT4 BDC and
install a new BDC. Once you have done this you need to disconnect your
current Win2k domain controller physically form the network. You then need
to do your migration over to Windows 2000. Promote a nt4 BDC to PDC and
upgrade that machine to Win2k and this will recreate your Win2k Active
Directory, making sure to keep the original Win2kDC offline. Make sure that
the new NT4 PDC does not have a domain name listed under TCP/IP properties
then the DNS tab. This domain name filed needs to be blank. Once this NT4
PDC is upgraded to Win2k and the dcpromo process starts you need to use an
FQDN domain name like 48-dom-mdtitle.local as the DNS name of the Active
Directory. This will make sure that you have a correct FQDN domain name for
your internal network. After you have succesfully migrated this box to Win2k
and Active Directory you can take the original Win2kDC and run dcpromo and
say it is the last domain controller for the domain and this will make this
machine a stand alone server, make sure this machine is NOT connected to the
network during this process. Once it is back to a regular stand alone server
and Active Directory has been removed you can run the Dcpromo process on
this box and it will back to a domain controller with the correct DNS
namespace and the box you used to get here (the NT4 PDC) can either be
removed or continue to run as an additional Domain Controller or you can
move the FSMO roles over to the original Win2kDC that was brought back in as
a Domain Controller and the NT4 PDC machine can be removed from the domain
if needed. The following articles will help too.

http://support.microsoft.com/default.aspx?scid=kb;en-us;254680&Product=win2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;285983&Product=win2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;260371&Product=win2000




--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

scrockel@***No_SPAM***hotmail.com
 
The existing DC is already a 2k server machine, but it was
upgraded from NT 4.0. This was done before I was here. I
now am having an issue where I have multiple computer
names in the network but the new server is the only
machine with that name. I tried to flush the name with
nbstat -RR and nbstat -R.
 
Back
Top