Trying to add 2003 AD to 2000 AD - DNS issue?

[kjsingh]

I am trying to add a 2003 domain controller (along with two additional 2003 servers) in an environment that is already running 2000 AD. The 2000 domain is named, let's say, abc.corp; based on this, my 2003 domain is named abc.com. Would this naming convention potentially cause some sort of DNS issue? If so, what could I do to avoid conflict?

I currently have DNS and DHCP running in the 2000 environment (abc.corp) but have these services disabled in the 2003 environment (abc.com) and tried pointing the 2003 servers' DNS to the 2000 environment; after some time, the 2003 domain controller starts acting weird, so I have now isolated the two environments, and everything is okay again. The goal is to eventually take away the 2000 domain and have users switch over to the 2003 domain, but the client needs the old and new servers to be running in parallel for some time first. Any help would be appreciated; thank you in advance.

 

[tfg13]

Why didn't you just add the 2003 AD to the 2000 domain as another DC? Seems as though you will run into problems because currently, you have two seperate domains. One is named abc.com, and the other abc.corp. Is the 2000 machine a GC? If so, you could in effect, add another domain named abc.com to the forest, and hope it replicates.

 

[pgoss]

It all depends on what you are trying to do. Currently you have 2 domains that have nothing to do with each other. What i think you need to do is bring the 2003 DC's up in the other environment. You need to make those DC's a part of the current 2000 environment and then retire the 2000 DC's.

-pat

 

[nephiB]

Of course the real problem is the NetBIOS name. I assume the existing environment is using ABC as the netbios name. the new one will have to use another. This is supported but hard to manage. So the win2003 domain, ABC.com (I think that's what you said) will have to use XYZ as the netbios name for the domain

Remember - Netbios is still with us!

 

[dearingkr]

One other thing to consider...

Adding a Win2k3 member server to a Win2k domain is no problem.

If you try to promote the Win2k3 servers to DCs, it will error. You will need to do a 'adprep' on the Win2k domain because the schema needs to be modified to Win2k3 standards.

I'm getting ready to do this myself this weekend. Will let you know how it goes.

MCSE CCNA CCDA