Re: AD <Automatically generated> site replication links

Hi Mathieu,

You can do this, but the AD does have a process that it follows when it
can't find a DC in the local subnet so you don't have to explicitly have to
do something unless it is very important for you to control this fail-over.

The order will be determined by the replication topology but will ultimately
end at the PDCe and the default-first-site.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
Chicago, IL

Remember: Marking helpful answers helps everyone find the info they need
quickly.


"Mathieu CHATEAU" wrote:

hello,

if you want all servers from unassigned subnet to go on one DC, you must
create a supernet.
Let's say 10.0.0.0/8, that you will bind to the DC main office.

When starting, a computer look for the most closer subnet. So if it find a
10.1.0.1/24, it will bind to it (and not to the default one).

When having mutliple site, you must always define one "super" subnet site
where all computers will default if nothing closer is available.
That also ensure that if one your site doesn't have any available DC, it
will connect to the main office DC and not another deported site.

Hope i am clear enough !


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"Nicolas Heyer" <NicolasHeyer@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F0243780-D91C-4F52-9624-577170414314@xxxxxxxxxxxxxxxx
Hello

we have several locations that are all connected to our central main
office
in a star tolopigy. All our windows DC server are installed with Windows
Server 2003 R2. Sites based on subnets have been created and we would like
all the servers in the outside locations to replicate from the main
office.

One server in our main office has all the 5 FSMO roles.

If we manually configure the site links to replicate as we would like it
to
be, we remark that after a few hours, the system creates additionally
<automatically generated> links where the main server is located outside
the
main office and connected over a "relative" slow link when compared to
other
links.

Why does AD ignore the actual configuration and tries to create its own
replication topology ? Is there a way to get over it ?

Thanks for any reply
Nicolas


.

Relevant Pages

  • Re: AD Traffic
    ... One subnet is 192.168.4. ... | There is windows xp workstation with ip 182.168.8.23. ... there is a windows server 2003 EE server. ... |> SBS 2003 box has two nics. ...
    (microsoft.public.windows.server.networking)
  • Re: WebDav problem maybe?
    ... They are both on the same subnet and on the same domain. ... Now Router configuration I didn't look into. ... Windows Server - File Storage ...
    (microsoft.public.windows.server.general)
  • BEST PRACTICES: Simple File Server
    ... This server has two network cards in it, one going to the p rivate subnet ... It is not necessary for the Corporate LAN to be able to access the private ... I am no a Windows expert here, ...
    (microsoft.public.windows.server.general)
  • Re: RRAS ip routing and ISA
    ... I have an dual homed ISA 2006 enterprise server acting as an edge ... I would like to join another internal subnet, ... stand-alone server as a DHCP server as long as it is not on a subnet ...
    (microsoft.public.windows.server.networking)
  • Re: AD Traffic
    ... One subnet is 192.168.4. ... There is windows xp workstation with ip 182.168.8.23. ... there is a windows server 2003 EE server. ... > SBS 2003 box has two nics. ...
    (microsoft.public.windows.server.networking)
Loading