Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problems setting up a 2K BDC for a NT PDC (Help!)

Status
Not open for further replies.

MaeMae

MIS
Jan 26, 2006
8
US
I am trying to set up a BDC for our PDC. Our PDC is set up on Win NT server and I am trying to set up a BDC on Win 2K advance. I can see the BDC on the PDC but I can't connect to the PDC from the BDC. And a more pressing problem is that when I am configuring Active Directory I get an error ("The domain is not an active directory domain,or an Active directory domain controller for the domain could not be contacted.) Our domain uses underscores which is no longer supported by win 2K active directory. How do I resolve this situation. The outcome is that we will promote this BDC to the PDC but only after we have everything in place. I have read some of the material on migration to server 2003 but the migration plan is to stay with win 2000 advance. PLEASE HELP. %-)
 
The situation you have at present, is as follows:

You have an NT4 domain, running a single PDC, and no BDC's. You also have a member server which is running 2003.

You are suggesting that you are going to move all the users data from the NT4 server to the 2003 server, and recreate all the necessary shares, and access rights, plus any printers set up on the PDC.

If I have got the above senario correct, then yea, your users will be able to access their files, and still log on with the same passwords and user names.

However, once you switch off the NT4 server, the only copy of the user accounts will no longer be available, and there will no longer be a domain.

If the NT4 server is then returned to the network, once again the domain will be available, and users will still be able to log on.

If you are intending doing this, consider the following.

1. Schedule some down time

2. Copy the files over from the NT4 Server to the 2003 server overnight, possibly with only these two machines on the network (seperate switch) in order to ensure no one accesses the NT4 server

3. Use DCPROMO tool to upgrade the 2003 to an AD domain controller

4. Recreate all user names, shares, and access rights

5. notify users of what their new passwords are.

So often times it happens that we live our lives in chains
And we never even know we have the key
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top