Setting up remote site

Posted on 2007-07-21
Last Modified: 2010-04-18
We are adding a remote site with a T1 line and 10 employees. We have our home site with a DSL connection and 40 employees. Our home site has a WIndows 2000 server we are upgrading to 2003 R2 and using Active Directory. We are adding a 2003 R2 server to the remote site. I am trying to figure out the best way to connectt e 2 sites. Should we keep 1 domain and replicate across the internet every few hours, should we create a totally separate domain and keep both sites under one tree, or is there some other option we should be looking at? I would like to allow anyone to go from one site to another and be able to login without having to maintain multiple accounts, but I am not sure how other places do this. Thansk for the help.
Question by:judsoncollege
    LVL 7

    Accepted Solution

    There is a couple ways you can do this...

    1. You can keep one domain, set up AD replication sites for your two different locations. The plus side of doing this is that if one domain controller goes down you still have another one you can use to authenticate. Also, doing it this way you only have one list of user accounts and passwords.

    2. You can have a domain for each site  and set up a two-way trust between the two domains. In this configuration, if someone came from the remote office (or vice versa) to your home office when logging in they would have to change the domain selection to their domain. In this configuration, however, if the domain controller went down for that domain since there would be no backup domain controller you'd better hope that you had up to date backups of the domain controller because you would have to reconfigure the entire domain.

    I would probably choose to stick with the single domain for redundancy issues and ease of operation. If you have any questions just let me know.

    Hope this helps!
    LVL 13

    Assisted Solution

    Stick with the single domain and DC in both offices as carcenea mentioned.  You may want to upgrade your HO DSL line to a T1 as well.   You will need to setup a site-to-site VPN between the two offices.  There are several routers out there that will do the site-to-site VPN including Cisco ASAs, SonicWALL, Juniper, and Netgear.  If you don't have a DC in both offices if the Internet goes down in one of the offices your VPN will drop and the Remote Office will not be able to authenticate to the HO and access files on their network.  

    Author Comment

    Thanks guys.

    Featured Post

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    Join & Write a Comment

    Preface Having the need * to contact many different companies with different infrastructures * do remote maintenance in their network required us to implement a more flexible routing solution. As RAS, PPTP, L2TP and VPN Client connections are no…
    Scenerio: You have a server running Server 2003 and have applied a retail pack of Terminal Server Licenses.  You want to change servers or your server has crashed and you need to reapply the Terminal Server Licenses. When you enter the 16-digit lic…
    how to add IIS SMTP to handle application/Scanner relays into office 365.
    In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor ( If you're interested in additional methods for monitoring bandwidt…

    729 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    16 Experts available now in Live!

    Get 1:1 Help Now