Having problems with AD Sites

  • Thread starter Thread starter Toby Tapp
  • Start date Start date
T

Toby Tapp

We have tried twice and failed to use sites as a way to insure users
authenticate to DC's in their subnet. The first time through I created the
sites and subnets and moved the appropriate DC in to that site. It seemed
to work, that is users would always authenticate to their local DC. At
first I was using the DefaultIPsitelink for all sites, but replication
between the DC was very slow. If it wasn't for VPN users that wouldn't
bother me much, but they would grab a random DC and if they got locked out
or changed their password it would replicate to the other DCs. Then I
started messing with site links and all of a sudden Exchange 2000 stopped
working, so I tucked my tail between my legs and put everything back the way
it was. About a week later and after much reading I tried again. This time
however users would not authenticate to their local DC, it was as if I
hadn't created any sites. This time around I created a bunch of site links
between the DCs and when I noticed it wasn't working I got rid of them and
went back to one site link for all servers. This didn't help again, so once
again I took everything back to square one. From all the stuff I read it
appeared I was doing it right, but I must have done something wrong as it
wasn't working. Any advice would be appreciated. Thanks
 
Also, what controls the automattically generated replication connections for
the servers? For some reason one of my remote DCs will create a bunch of
connections to every other DC.
 
Back
Top