Can't log in using second domain controller when first DC is unreachable
- by rbeier
Hi,
We're a small web development company. Our domain has two DCs: a main one (BEEHIVE, 192.168.3.20) in the datacenter and a second one (SPHERE2, 10.0.66.19) in the office. The office is connected to the datacenter via a VPN.
We recently had a brief network outage in the office. During this outage, we weren't able to access the domain from our office machines. I had hoped that they would fail over to the DC in the office, but that didn't happen. So I'm trying to figure out why. I'm not an expert on Active Directory so maybe I'm missing something obvious.
Both domain controllers are running a DNS server. Each office workstation is configured to use the datacenter DC as its primary DNS server, and the office DC as its secondary:
DNS Servers . . . . . . . . . . . : 192.168.3.20
10.0.66.19
Both DNS servers are working, and both domain controllers are working (at least, I can connect to them both using AD Users + Computers).
Here are the SRV records that point to the domain controllers (I've changed the domain name but I've left the rest alone):
C:\nslookup
Default Server: beehive.ourcorp.com
Address: 192.168.3.20
set type=srv
_ldap._tcp.ourcorp.com
Server: beehive.ourcorp.com
Address: 192.168.3.20
_ldap._tcp.ourcorp.com SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = beehive.ourcorp.com
_ldap._tcp.ourcorp.com SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = sphere2.ourcorp.com
beehive.ourcorp.com internet address = 192.168.3.20
sphere2.ourcorp.com internet address = 10.0.66.19
Does anyone have any ideas?
Thanks,
Richard