Is there a configuration that would allow branch office users to logon when the branch's domain controller is unavailable without adding a second domain controller at the branch? Single domain, Windows 2003. Thanks in advance.
Software/Hardware used:
ASKED:
February 25, 2007 10:10 PM
UPDATED:
February 26, 2007 7:17 PM
I agree. We have a domain controller at each remote campus and if it goes down, the clients can still reach the domain controllers at the main campus through our leased links. The other part of this is configuring the client systems to list all of the domain controllers as DNS servers. I have recommended a policy of entering all of the domain controllers in every client and putting the local one at the top of the list. This model assumes you are using the domain controllers as DNS servers for the clients.
rt
Thanks for the responses-
There is a routed point-point T1 link between the main office and the remote office. None of the traffic is filtered. Each domain controller at each site provides DNS. I will need to check on the remote’s client DNS settings to confirm if a main office DNS server is included.
I have created sites in AD and AD replication is working fine.
Any more information I can provide?
Thanks again.
Scott:
The setup looks good. I suspect the main issue is configuring the clients to use the remote servers. You can do a partial test by configuring a client to use only the remote server for DNS. If this works you should be fine. If you want to be completely sure, I would bring down the office DC some night and test logins with its clients.
rt