finance_teacher
asked on
Windows Server 2012 -- domain controller FAILOVER ?
My two 50-user locations are connected via
20MB fiber and each has ONE domain controller.
How can I setup so if an ON-SITE domain controller
is down it uses the REMOTE domain controller instead
or do I need two domain controllers at each location ?
20MB fiber and each has ONE domain controller.
How can I setup so if an ON-SITE domain controller
is down it uses the REMOTE domain controller instead
or do I need two domain controllers at each location ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
also does DNS for the 50 users at each site.
Site #1 Example, 192.168.1.1
** Primary DNS Server = Site #1, 192.168.1.1
** Secondary DNS Server = Site #2, 192.168.2.1
--------------------------
What do you recommend since it seems like the below happens ?
** login to a computer @ site #1 using a NEW, non-cached account
** see that above Primary DNS Server & Secondary DNS Server are correct
** turn off Primary DNS Server
** login to a NEW computer @ site #1 using a NEW, non-cached account
** login as the CACHED user instead
** do PING
** 192.168.1.1 is down
** 192.168.2.1 is up
I was assuming login to a NEW computer @ site #1 using a NEW,
non-cached account would work since the backup, 192.168.2.1, is up