Branch office logon

scottbr
pts.
Tags:
Active Directory
Microsoft Windows
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.
Asked: Last updated:
Related Questions

Answer Wiki

Thanks. We'll let you know when a new response is added.

Short answer is yes, but. You did not provide a full description of your network. We would really need to know how your network is configured. For example, if you have a VPN between the branch and main office (like router to router not software) then the workstation could find a DC at the main office.
Just a thought.
dmw

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Astronomer
    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
    15 pointsBadges:
    report
  • scottbr
    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.
    0 pointsBadges:
    report
  • Astronomer
    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
    15 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: