Re: Numerous Replication Connections per DC/GC?
- From: "Ace Fekay [MVP]" <PleaseAskMe@xxxxxxxxxxxxxx>
- Date: Tue, 8 Aug 2006 01:26:57 -0400
In news:Xns9814705F4102DnoIDtoken@xxxxxxxxxxxxx,
SWalters <swalters24NOSPAM@xxxxxxxxx> stated, which I commented on below:
Ace Fekay [MVP] wrote:
I am currenlty documenting the subnets in relationship to the sites
as well. Unfortunately I can't say for sure if they are correct or
not. I am finding some rogue servers which were not demoted correctly
from AD and still have their identity in some sites but I'm hoping
all subnets are correct...time will tell.
Most of the Sattelite sites have only one DC/GC so they obviously are
the bridgehead servers for their site. However, there are at least 30
"Hub" sites which have multiple DC/GCs.
Based upon what you said above let's say you have a HUB site with 4
GC/DCs (not all will be GCs) and a SAT site with only one GC. Now
that SAT site has only one Site Link which connects it to the above
mentioned HUB site. THat server in the SAT site should have how many
connections? Should those connections ONLY be to that HUB site and
not other sites in any domain?
One other note on the "Disable ISTG" comment. I don't think I want to
disable ISTG fully. It's my understanding that if ISTG creates
something that is not needed you can manually delete that connection
without ISTG recreating it at a later date. I also was thinking this
problem could be stemming from the "Bridge all site links" option
being utilized. If all site links are being bridge that would mean
ISTG can and will create connections to any server from any
site...right?
Sorry for the late reply.
As for the numerous removed DCs, it seems that they were just unplugged and
not properly removed by demoting them. The old references must be removed by
using the Metadata Cleanup process:
216498 - HOW TO Remove Data in Active Directory After an Unsuccessful Domain
Controller Demotion (2000):
http://support.microsoft.com/?id=216498
Clean up server metadata Active Directory 2003:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Operations/012793ee-5e8c-4a5c-9f66-4a486a7114fd.mspx
I would leave the ISTG alone, as Andrei suggested. Let the KCC create the
connections.
The subnet objects must be set properly. Also, DNS is important for AD
functionality. Make sure all machines onlyuse the internal DNS and not an
ISP's DNS anywhere in IP properties or anywhere else other than as a
forwarder.
The one hub and one sat site would have probably two connections. One
between the bridghead in the hub connected tothe bridghead in the remote
site, one one for the bridgehead in the remote site connecting to the
bridghead in the hub. As Andrei also said, should only have a minimal amount
of connections. Site Bridge links are like shortcut links between sites in a
linear design, such as Site A to SiteB to SiteC. You can create a shortcut
between C and A by bridging them. But you should have 115.
If you can post or send me a Viso of your layout, along with the names of
all your DCs and their ipconfig /alls, I can help to diagnose and optimize
it. Also send me a snapshot of Sites and Services with your Sites and IP
Subnet objects expanded. Send it to my email address. It's my
firstnamelastname(no spaces or periods)@hotmail.com.
Ace
.
- Follow-Ups:
- Re: Numerous Replication Connections per DC/GC?
- From: SWalters
- Re: Numerous Replication Connections per DC/GC?
- References:
- Numerous Replication Connections per DC/GC?
- From: SWalters
- Re: Numerous Replication Connections per DC/GC?
- From: Ace Fekay [MVP]
- Re: Numerous Replication Connections per DC/GC?
- From: SWalters
- Numerous Replication Connections per DC/GC?
- Prev by Date: gethostbyname
- Next by Date: Re: new users can't login
- Previous by thread: Re: Numerous Replication Connections per DC/GC?
- Next by thread: Re: Numerous Replication Connections per DC/GC?
- Index(es):
Relevant Pages
|
