dankyle67
asked on
changing domain controller clients use for authentication
HI,
recently, the domain controller for one of our remote sites was not able to replicate for few months since our vpn was down all that time so server tombstoned. I stressed to management the importance of not allowing vpn to be down this long but they didnt take my advice so anyway, now they have a dedicated high speed connection that bridges both our office sites so wanted to know how i can point the pcs in the remote site to use the main domain controller in the main office for domain authentication since they have been getting trust relationship errors in the past 2 weeks most likely due to losing connection our communication to the tombstoned domain controller so i thought by pointing to the main domain controller this would be fixed as well but just this morning when the tombstoned server went down actually, i was not able to rejoin one of the pcs to the domain after giving message that there no active directory domain controller for the domain cannot be contacted. Thanks.
recently, the domain controller for one of our remote sites was not able to replicate for few months since our vpn was down all that time so server tombstoned. I stressed to management the importance of not allowing vpn to be down this long but they didnt take my advice so anyway, now they have a dedicated high speed connection that bridges both our office sites so wanted to know how i can point the pcs in the remote site to use the main domain controller in the main office for domain authentication since they have been getting trust relationship errors in the past 2 weeks most likely due to losing connection our communication to the tombstoned domain controller so i thought by pointing to the main domain controller this would be fixed as well but just this morning when the tombstoned server went down actually, i was not able to rejoin one of the pcs to the domain after giving message that there no active directory domain controller for the domain cannot be contacted. Thanks.
Iradat Siddiqui
Please add a new domain controller with a different name at the remote site and join all the systems to the domain.
ASKER
I tried that but the new domain controller isnt able to replicate to the main domain controller at the main office site. The main domain controller was recently set up for test purposes as a vpn server so we had to enable the 2nd nic card on it so now that server is multihomed so would that cause a problem with replication since maybe the new domain controller i set up last week cant find the main domain controller properly? I also never did a restart of the new domain controller when i created it so should i do that?
check if AD authentication ports are opened between remote site client subnet and main office DC
On the DC in main office, in network card advanced binding order, keep local production network card at top.
Then reboot the DC once and then try to promote ADC at remote site
On the DC in main office, in network card advanced binding order, keep local production network card at top.
Then reboot the DC once and then try to promote ADC at remote site
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.