Hello grahamstein,
Ok, so you have two total different forest/domains with the same name private.xxx.xxx
and both have there own NetBios name. This domains cannot be connected as
Florian states and you have to decide which one you like to use. If there
is the need for keeping objects use LDIFDE as Florian stated.
http://support.microsoft.com/kb/555636
If there is no need to keep AD from one then copy/backup the data you need
and format the machine during reinstall and make it member of the exisiting
domain where you can promote it to DC again.
Also i suggest to run the support tools dcdiag /v and netdiag /v on the DCs
to check if errors exist.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
> From what i am told/nearest i can figure is that at one point server A
> had the OS crap out. A fresh install was done, and rather than join
> the existing forest when installing AD, it was installed as a brand
> new forest with the same name as the already existing domain.
>
> So we seem to have 2 domains of the same name (private.xxxx.xxxx)
> existing on the network with different netbios names and i am trying
> to find some way to at least get AD replication working between the 2
> without having to reinstall the OS on either.
>
> http://forums.techarena.in
>
Similar Threads
Linear Mode
