Increase Replication

  • Thread starter Thread starter Dan
  • Start date Start date
D

Dan

I have 3 DC, one in City A and two in city B. the distance between the two
cities is 12 miles. I have 2 T1 lines connected in Multilink Point to Point.
(3MB) when i add a user in city A DC some times it taked like 6 min to
replicate to the other DC. Also some times when users in City A log in they
authenticate from City B. I need to know how i can make the replication
faster and how do i make users in City A authenticate from City A.

thanks
 
<snip>
Dan, are the DCs in the two cities in separate sites?

--
Cheers,
Marin Marinov
MCT, MCSE 2003/2000/NT4.0,
MCSE:Security 2003/2000, MCP+I
-
This posting is provided "AS IS" with no warranties, and confers no
rights.

"True knowledge exists in knowing that you know nothing."
Socrates
 
If you are running W2K, 6 minutes isn't bad. To get it to go faster you have to
change some registry entries to speed up the change notification replication
system. See http://support.microsoft.com/default.aspx?scid=kb;en-us;214678


You don't say anything about your configuration so I would guess you are using a
single site.

In order to fix the issue with your clients you actually have to build separate
sites for the cities. That way the clients know which DC is the right one to
use. Now what this will do by default is slow down replication time. However you
can override that by then enabling change notification across the site link
which will bring you back to where you were above.
 
Do all the 3 DCs belong to a single domain? do you have 2 different sites
configured? the reason why the users in city a authenticating to servers in
city b is because you need a GC server in city a, you need to make the
server in city A a GC server. AD has multimaster replication and the time
for any inter domain replication between DC is 5mins. the repication
topology is generated autoamtically by KCC. If you have 2 different site for
these 2 cities, then you can make one server in each city a bridgeheard and
configure the replication settings( intervals etc). You can also force
replicate between two sites to update all DC in both cities real-time.

-Jim
 
Dan said:
This setup is one domain, One site.
Click to expand...

Your setup should not be limited to the default_first_site in your case. W2K
is not aware of the physical aspects of your network by default. Thats why
sites were introduced to provide a method to describe and control a W2K
network architecture via a network's physical topology(using subnets). Sites
let you control both replication schedules between sites and confines a
user's login to that site's DCs.
 
Back
Top