Re: Creating Remote sites Properly

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Cary Shultz [A.D. MVP] (cwshultz_at_mvps.org)
Date: 08/10/04


Date: Tue, 10 Aug 2004 19:02:18 -0400

Brian,

This *may* be a little bit different in WIN2003 but here is how you do it in
WIN2000.

Create a Site for your first 'remote' subnet. Let's call this Miami.
Associate the 10.1.2.x subnet to the Miami Site.

Create a Site for your second 'remote' subnet. Let's call this one Atlanta.
Associate the 10.1.3.x subnet to the Atlanta Site.

Create a Site for your third 'remote' subnet. Let's call this one Columbia.
Associate the 10.1.4.x subnet to the Columbia Site.

Let's say that your HQ is in Charlotte. If you have not already done so,
create the 10.1.1.x subnet and associate it with the
Default-First-Site-Name. You can rename this to Charlotte if you so choose.

We are going to use the hub and spoke model. This is where Charlotte is the
hub and all of the Sites are connected to Charlotte. It would be a really
good idea to have a Firewall at the Charlotte Site that can handle multiple
VPNs as you should strongly consider creating a Site-to-Site VPN from
Charlotte to Miami and a second VPN from Charlotte to Atlanta and a third
VPN from Charlotte to Columbia. You would also need a Firewall at the three
remote locations that can handle the VPN ( doh ). Cisco and SonicWall have
some nice products.

You need to make sure that the Domain Controller in each Site has the proper
IP Address ( I am sure that you are using either a Reservation or a Static
IP Address for all of your servers ) and is located in the correct Site in
the ADSS MMC..

You would probably want to make each of the Domain Controllers a Global
Catalog Server as well. DNS would also be important. Probably DHCP as
well.

Please take a look at the following MSKB Articles on how clients locate a
Domain Controller:

http://support.microsoft.com/?id=247811
http://support.microsoft.com/?id=314861

Our friend the KCC - with a little help from the ISTG - will make sure that
everything is done properly. However, it is extremely important that the
Sites and Subnets be set up and configured properly. The KCC uses this
information. The one thing that you would need to do would be to set up the
Site Links. There would already be one ( the DEFAULTSITELINK ) that is
partially set up. You would need to add the second Site ( you will see that
Charlotte is already there - you would simply add Columbia, for example ).
You would then set up another Site Link for Charlotte - Atlanta and a third
for Charlotte - Miami. You would need to create the Costs as well as the
Schedule and the Intervals associated with each Site Link. You will want to
think about bridging all Site Links.....

This is a pretty vanilla account of what you could do. We would need a lot
more information from you in order to give you a more appropriate response.

How many users are in each Site? What are the client OSes? What are the
connection speeds between each location? Do you want / need all Sites to be
linked to the others? You get the picture.

HTH,

Cary

"Brian" <brian21@elvis.com> wrote in message
news:c0db3671.0408101430.503f1dfd@posting.google.com...
> I have a question regarding setting up remote sites in AD sites and
> services.
>
> I have 3DC's in corp office on same subnet
>
> I also have 3 seperate remote offices with a DC in each. My question
> is how should I setup the replication topology between the remote
> sites and corp office. Right now I have many clients who authenticate
> across the lan to a remote DC, and I would like to correct this.
>
> All domain controllers currently run windows 2003 server
> One DC in corp office hosts Primary DNS
> One DC in corp office hosts Secondary DNS
>
> 3 DC's in corp office. 10.1.1.x
> remote office 10.1.2.x
> remote office 10.1.3.x
> remote office 10.1.4.x



Relevant Pages

  • Re: Creating Remote sites Properly
    ... Remote Offices all have 30-50 users connected by redundant T1 Wan ... > Associate the 10.1.2.x subnet to the Miami Site. ... Let's call this one Atlanta. ... > Let's say that your HQ is in Charlotte. ...
    (microsoft.public.win2000.active_directory)
  • Re: LAN routing
    ... No - never had a VPN inplace. ... The remote office is expanding as is the main office. ... > LAN?,...or just adding a new subnet to what they already have?,...that is ...
    (microsoft.public.windows.server.networking)
  • Re: Assign a Win2003 server with a remote IP address in a differen
    ... Yes, i forget the ADSS, when you have configured the new ip for remote site and shutdown, also move the dc to the respective subnet in ADSS. ... If you then startup the server the basics should be correct. ... The remote office has its own dedicated lan setup already. ...
    (microsoft.public.windows.server.general)
  • Re: Connecting a remote workstation to a domain
    ... then ship to the remote office but the remote office computers were ... do this using a profile pre-configured on the server LAN then copied ... Make sure users understand that they should not log into multiple computers ...
    (microsoft.public.windows.server.sbs)
  • Re: Do i need to create a site in AD?
    ... site, in AD, do i need to configure my network id and subnet for the ... Replicate. ... domains in the AD forest. ... We now are connecting a remote site ...
    (microsoft.public.windows.server.active_directory)