NT>2k3 migration namespace problem

  • Thread starter Thread starter ehansen
  • Start date Start date
E

ehansen

hello

We recently tested a NT4 pdc to win2k3 AD migration and
had a problem with the namespace. the NT4 domain was
called "test-dev1" we upgraded to 2k3 and it auto
dcpromo'd and when we got to changing the namespace we
changed it too "cert1.net".

After the migration, on the domain controllers in the
network properties it says "Domain : cert1.net" as it
should, but the test client machines that were previous
members of the NT domain could not log into "cert1.net"
and would only log into "test-dev1".

Also any new machines joined to the AD had to join the
domain "test-dev1" and NOT "cert1.net"

why?

any help is greatly appreciated.

e-
 
It sounds like you probably have a disjointed name space problem on your
upgraded domain controller. To see if this is the case, please check the
following:
On your DC's desktop, right click My Computer and choose properties. Then
go to the network identification tab. Your computer name and domain name
should look similiar to:

Full Computer Name: servername.domainname.com
Domain name: domainname.com

If your server name does not include the proper fully qualified domain name,
then you have a disjointed name space. This is a common problem on upgraded
domain controllers. If this is the problem you have, you will need to
contact Microsoft technical support and they should be able to open you a
grace case to get the disjointed name space script to correct the problem.
If they cannot open a grace case for you, then once you speak with a MS
support professional, they will be able to refund the cost of the case if
all you need is the disjointed name space script.

If this is not your problem, then make sure that you have DNS installed on
your upgraded Domain controller. In Windows 2000, DNS is critical to making
active directory work properly. Make sure that your upgraded DC points to
itself for DNS. You can then configure your DNS server to forward requests
out to the internet. Make sure that all your other clients and servers in
your domain point to your upgraded DC for DNS as well.

One last thing concerns the domain name that your users log into. You said
that test clients could not log onto "cert1.net" but could only log onto
"test-dev1". If I understand your situation, then this is normal. When you
upgrade a domain from NT4 to 2000 or 2003, your netbios domain name will
stay the same (test-dev1) but you will now also have a FQDN (cert1.net).
You clients will continue to see the test-dev1 domain name when they logon.

The problem with only being able to join clients to the test-dev1 domain is
most likely because of a DNS misconfiguration. I explained how to set up
DNS to avoid this problem.

I hope this helps.

Ray Lava
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights
 
Back
Top