Re: AD <Automatically generated> site replication links

Hi,

Thanks for the information. When you state "I have created an IP SITE LINK
" is this just one site link with the three sites in it? Just to clarify, I'm
not talking about the manual links (i.e. manual connection objects you've
created between DCs) - rather the site link(s).


"Nicolas Heyer" wrote:

Hello everyone

first of all i would like to thank you all for your answers. As I wrote it
yesterday, I found the article 242780 in the MS knowledge base, applied it on
all sites and was pretty sure, this would solve my problem... but the site
links were created once again this morning. So I try to be a little more
explicit and tell you how our topology is and how I would like our AD to be
replicated. I simplify it a little as we have 8 locations in real, but let's
talk about 3, it resumes already my problem:

I have a main location in Basel with two Domain Controllers (several subnets
in the same site)
I have a location in Zurich with 1 DC (one subnet)
I have a location in Wien with 1 DC (one subnet)

I have created the 3 sites and associated the subnets to their sites.
I have created an IP SITE LINK (schedule the whole day, every 120 minutes,
costs: 100)
I have created a manual link from each DC in our central location to each
server on our outside locations:

Basel1 ---> Zurich1 (IP replication every 15 minutes the whole day)
Basel1 ---> Wien1 (IP replication every 15 minutes the whole day)
Basel1 ---> Basel2 (IP replication every 15 minutes the whole day)

and

Basel2 ---> Zurich1 (IP replication every 15 minutes the whole day)
Basel2 ---> Wien1 (IP replication every 15 minutes the whole day)
Basel2 ---> Basel1 (IP replication every 15 minutes the whole day)

After some hours, the system created an <automatically generated> link in
almost each site where Wien1 is the source server.

Though all the physical links come and go from/to Basel, this isn't a good
thing. So I used the article described before to modify with LDP.EXE the NDTS
settings of each site by entering the "option" parameter with the value 16:
this should prevent the KCC from created those <automatically generated> site
links between different sites. But it seems to have no effect.

The modification were taken and the commands I entered did show no error
when interpreted by the system, but I would like to be sure the KCC doesn't
act anymore but I did not find exaclty in the replication monitor, which
option to use to verify if everything has been set.

So I'm still in the "cold" this morning. If someone could help me.

Regards
Nicolas



"Ryan Hanisco" wrote:

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 site replication links
    ... OK...to get back to normal...I would move one server at a time back to its ... correct site and ensure that replication is working before moving anymore. ... links, force a KCC check and a forced synchronisation, the whole thing is ... I have a location in Zurich with 1 DC (one subnet) ...
    (microsoft.public.windows.server.active_directory)
  • Re: New Remote Office
    ... Say you have two AD sites called site1 and site2, where site1 represents a central site with multiple subnets and site2 represesnts a remote office with a single subnet. ... -Sites constrain replication between DCs and prevent replication traffic from hogging bandwidth. ... taking the server to the remote site to perform DC promo there. ... Are there likely to be any DNS issues with the new remote server connecting ...
    (microsoft.public.windows.server.general)
  • Re: AD site replication links
    ... synchronisation delay to 15 minutes to reflect the manual links I've created. ... I have a location in Zurich with 1 DC (one subnet) ... almost each site where Wien1 is the source server. ... The order will be determined by the replication topology but will ultimately ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD site replication links
    ... I have a location in Zurich with 1 DC (one subnet) ... almost each site where Wien1 is the source server. ... The order will be determined by the replication topology but will ultimately ...
    (microsoft.public.windows.server.active_directory)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.sbs)
Loading