NT4 BDC Upgrade to Windows 2000 DC

M

Man Geekaa

After I sucessfully upgraded NT4 pdc (srv1 & domainX) to 2000 advanced
server DC (newdomainY.org) with integrated DNS. And now when I am upgrading
the other remaining NT4 BDC (srv2) to act as second 2000 advance server DC,
it fails at the very end of the upgrade process when the active directory
migration (dcpromo) wizard tries to look for 'srv2$' account in
'newdomianY.org with an error saying no domain controller found for
'newdomainY.org'

Also all client computers indicate they are now members of 'newdomainY.org'
and each of them has two domain logon option - 'domainX' & 'newdomainY'
(note: '.org' is missing in domain name 'newdomainY' that is being dispayed
in login box). Though I always succeed in logging into 'domainX' but have
never been sucessfull when I choose 'newdomainY' for authentication.

Currently our network is running with only ONE 2000 DC as I have been
unsucessfull in configuring a new 2000 advanced server box to act as second
2000 DC for 'newdomainY.org' using dcpromo wizard, the error message
indicates the same as above that no domain controller found for
'newdomainY.org'.

My end goal is to have a second 2000 DC in our enviroment ?


Regards,

-MGK
 
G

Guest

There is a common problem when NT 4.0 PDC's are upgraded to Windows
2000/2003. The problem is that the Fully Qualified Domain Name (FQDN) on the
NT 4.0 PDC did not match the FQDN of the domain when you upgraded. The
result is that the only Windows 2000 Active Directory Domain controller in
the domain cannot properly register with DNS. To see if this is your issue
click on My Computer and click properties Click on the Computer Name tab.
Check out what the full computer name says. If it does NOT match the name of
the AD domain, that you have the problem described. To illustrate further,

if I have a PDC called myserver. It has a FQDN of myserver.company.com. I
upgrade the sever to Windows 2000 and make a Active Directory domain call
MyCompany.NET. The upgrade process will never check that the two names are
compatible. The domain controllers names will be retained as
myserver.company.com, but the AD is created as MyCompany.NET. The myserver
can never properly register or even complete the upgrade to AD while its name
is myserver.company.com. Further, since this is a domain controller you have
no way to change the name.

To resolve the problem you will have to erase the server, then promote one
of the NT 4.0 BDC's to a PDC, then rebuild the server as a BDC in the NT 4.0,
then promote the server to PDC. Finally, make sure the FQDN of the NT 4.0
server matches what you will be calling the AD. Then, upgrade the server to
Windows 2000.

Now - if this isn't your problem because myserver.MyCompany.NET matches your
AD name - well then you likely have a simplier issue in that DNS is mixed up
somehow. This can be the case when you do the installation at the same time
that you are upgrading the server. Make sure that there is not root domain
listed in the DNS. A root domain is signified by a single dot ".". This
means that it is the end-all--be-all domain for the entire Internet, not
likely I would say. You would delete this domain and reboot the server.

There is some assistance in diagnosing problems by using the DCDIAG and
NETDIAG in the Windows 2000 Support Tools found on the Installation CD.

Cheers,
 
C

Cary Shultz

Paul,

Just saw the bottom of your post. It was a really good idea to use the
Support Tools. They are a huge part of what I do. But, it is better to
install the Support Tools from the latest Service Pack CD or via download
from the MS web site. The Support Tools on the original Server CD-Media are
a bit outdated ( and have some known issues ).

--
Cary W. Shultz
Roanoke, VA 24012

http://www.activedirectory-win2000.com
(soon to be updated!!!)
http://www.grouppolicy-win2000.com
(soon to be updated!!!)
 
J

Jorge_de_Almeida_Pinto

After I sucessfully upgraded NT4 pdc (srv1 & domainX) to 2000
advanced
server DC (newdomainY.org) with integrated DNS. And now when I
am upgrading
the other remaining NT4 BDC (srv2) to act as second 2000
advance server DC,
it fails at the very end of the upgrade process when the
active directory
migration (dcpromo) wizard tries to look for 'srv2$' account
in
'newdomianY.org with an error saying no domain controller
found for
'newdomainY.org'

Also all client computers indicate they are now members of
'newdomainY.org'
and each of them has two domain logon option - 'domainX' &
'newdomainY'
(note: '.org' is missing in domain name 'newdomainY' that is
being dispayed
in login box). Though I always succeed in logging into
'domainX' but have
never been sucessfull when I choose 'newdomainY' for
authentication.

Currently our network is running with only ONE 2000 DC as I
have been
unsucessfull in configuring a new 2000 advanced server box to
act as second
2000 DC for 'newdomainY.org' using dcpromo wizard, the error
message
indicates the same as above that no domain controller found
for
'newdomainY.org'.

My end goal is to have a second 2000 DC in our enviroment ?


Regards,

-MGK

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

The DNS suffix of the computer name of a new domain controller may not
match the name of the domain after you install upgrade a Windows NT
4.0 Primary domain controller to Windows 2000.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top