BDC Question

This cannot be done with NT 4. Domain controllers cannot join another domain. A domain controller IS a domain controller whether PDC or BDC. The only difference is that at any one time only one of the DCs can have a non-read-only copy of the SAM Database. And because a Domain controller embodies the domain, as long as one is still up and running the domain is still there. Therefore you cannot say that Domain 1 no longer exists whilst you still have a Domain controller for it. The only way to make that computer join another domain without having to re-install the OS is to upgrade it to Windows 2000 Server, then run DCPROMO to demote it. Once demoted, it can be made to join a different domain. Sorry, dude, there is no other way!

Yes it is.
Stop replication on all servers in domain2,
and on the bdc.Go into network neighbourhood/properties on the bdc - ge domain.Restart replication.That's it very simplified but Microsoft have Technet articles about this.If I can dig them out I will repost

Further to previous mail the article
Q178009 should be of interest.It is about changing the name of an entire domain, but you just need the bit about the bdc.Hope this helps

Everyone seems to be beating around the bush. The short answer is to use the NT Rescue disk created during the installation of NT - (not the boot disk set.) or in fact a previous hardware profile, (if any.)
Basicly get into NT any which way you canand change the name or Network ID of the BDC.
Once reconfigured and rebooted, it can be setup as a BDC for any other domain in the usual way.

This question was auto closed due to inactivity