Moving to a new domain

[Guest]

Hi

I have a Windows 2000 AD domain of about 50 users and PC's, all Win 2000 & XP. The domain consists of 1 Domain controller and several Windows 2000 servers. The domain and dns have been set up incorrectly - the Active Directory domain name is domainname.com - rather than something.domainname.co

This causes us major problems with DNS and everything else

I want to create a new domain on a new server, and then move everyone to the new domain, and then scrap the old domain. But... because DNS is so screwed up the Active Directory Migration tool doesnt work

Are there any issues in moving to a new domain? We have a few file servers, web servers and SQL servers on the network

Any advice anyone could give me would be appreciated

Thanks

Will

 

[Cary Shultz [A.D. MVP]]

Will,

I am not sure why having domainname.com will cause you any issues. While it
might not be the best solution ( there are those who will tell you that
domainname.local - or something like that - is a better solution: this is
not really the place for that discussion ) it definitely works very well.
That assume, naturally, that everything is set up correctly.

What exactly is messed up? Have you installed the Support Tools and ran
dcdiag and netdiag as well as repadmin and replmon. This should give you a
better idea of what is going on.

Let's take this approach first. It might just solve your problem and save
you ( and your user base ) potential down time.

HTH,

Cary

Hi,

I have a Windows 2000 AD domain of about 50 users and PC's, all Win 2000 &

XP. The domain consists of 1 Domain controller and several Windows 2000
servers. The domain and dns have been set up incorrectly - the Active
Directory domain name is domainname.com - rather than
something.domainname.com

This causes us major problems with DNS and everything else!

I want to create a new domain on a new server, and then move everyone to

the new domain, and then scrap the old domain. But... because DNS is so
screwed up the Active Directory Migration tool doesnt work!

Are there any issues in moving to a new domain? We have a few file

servers, web servers and SQL servers on the network.

 

[Guest]

Hi Cary

Thanks for your reply. The main issues i have been having are

Our internet domain name is the same as the AD domain name - therefore if we setup a new subdomain eg test.domainname.com then our local pc's cant resolve the subdomain. (we are a web design company so we are creating lots of different subdomains each day!

I have tried setting up new domain controllers, but cant get them to replicate between each other. I have been told that this is down to the domain name issue. I need to set up a new Exchange server - but cause this has to be installed on a DC I can't

I have installed the support tools and run NetDiag. This is the result

DNS test . . . . . . . . . . . . . : Faile
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '10.0.1.165'. Please wait for 30 minutes for DNS server replication
[FATAL] No DNS servers have the DNS records for this DC registered

It is an Active Directory Integrated DNS zone


Wil

 

[Lanwench [MVP - Exchange]]

Not sure what to tell you - you can't rename your AD domain - you'd need to
start over from scratch. Even in W2003, in which you can rename a domain,
you can't do it when Exchange is in the picture. Sounds like you need to do
some stuff in your AD DNS if you don't want to go that route -