I seem to have inherited a rather dysfunctional domain at my new job...heres the scenario:
There are 3 win2k DC's total, 2 on a local lan and the third linked via site ip. it seems that the 3rd dc has stopped replicating to it's partners...this wouldn't seem like to hard a problem to fix...however it seems to have been occurring for quite some time (replmon reports over 22000 objects haven't replicated) :|
This seems to have caused quite a few problems within AD (no kidding!!) as the 3rd DC is actually based in a hotlab where all machines are joined to the domain before being deployed to site. I've also noticed a problem with reverse-dns lookups where dns is keeping the ip of the newly built machine on it's hotlab subnet (all DHCP).
Anyone got any quick suggestions for a nice little fix? perhaps something i've overlooked?
(i was considering step#1: Uninstalling AD and rebuilding 3rd DC...and step#2: deleting the hotlab subnet and recreating it)
There are 3 win2k DC's total, 2 on a local lan and the third linked via site ip. it seems that the 3rd dc has stopped replicating to it's partners...this wouldn't seem like to hard a problem to fix...however it seems to have been occurring for quite some time (replmon reports over 22000 objects haven't replicated) :|
This seems to have caused quite a few problems within AD (no kidding!!) as the 3rd DC is actually based in a hotlab where all machines are joined to the domain before being deployed to site. I've also noticed a problem with reverse-dns lookups where dns is keeping the ip of the newly built machine on it's hotlab subnet (all DHCP).
Anyone got any quick suggestions for a nice little fix? perhaps something i've overlooked?
(i was considering step#1: Uninstalling AD and rebuilding 3rd DC...and step#2: deleting the hotlab subnet and recreating it)