Re: Replication Issues with A/D
- From: "Jorge de Almeida Pinto [MVP - DS]" <SubstituteThisWithMyFullNameSeparatedByDots@xxxxxxxxx>
- Date: Sat, 24 Mar 2007 03:12:40 +0100
basically you are saying:
HUB and SPOKE model
HUB <---> SPOKES = OK
SPOKES <---> SPOKES = NOT OK because of no IP routing
so why should auto site link bridging be enabled? it should not be enabled
site link BRIDGING is that is connecting the spokes together and because
there is not IP routing, it fails, so disable site link bridging
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* How to ask a question --> http://support.microsoft.com/?id=555375
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"TS_Confusion" <TSConfusion@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:390E0CD0-6AAB-48C3-874D-6DA8A3C45EAE@xxxxxxxxxxxxxxxx
The sites and subnets are correct ( I have checked them 1000x) :)
Also, if I disable auto site link bridging for all sites, how will they
speak with each other?
"Jorge de Almeida Pinto [MVP - DS]" wrote:
setup sites and subnets correctly in AD, disable auto site link bridging
for
the IP protocol
do you also use DFS?
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* How to ask a question --> http://support.microsoft.com/?id=555375
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no
rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"TS_Confusion" <TSConfusion@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1D8F0D7B-AB4C-44CC-B675-9332A18BE1D9@xxxxxxxxxxxxxxxx
Hi!
I have posted a few times on this and figured I would put everything
into one post to make it easier. Now for the background on my network:
I have four subnets and each subnet is registered to a site in
Directory
Sites and services.
Site A's subnet can talk with ALL subnets in our network (B,C,D)
However, subnets associated wtih Site B, C, D cannot talk to any subnet
but
Site A's subnet.
So I have the following site links setup in AD Sites and services,
Site A to Site B
Site A to Site C
Site A to Site D
Now, the first problem I have is that Site D's domain controller (it
only
has one) is giving me the following errors:
"All servers in <SITE C> that can replicate partition
DC=authentify,DC=inc
over transport CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=authentify,DC=inc are currently
unavailable. "
Then:
"All servers in <Site B> that can replicate partition
DC=authentify,DC=inc
over transport CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=authentify,DC=inc are currently
unavailable.
Then finally I get the last error messages:
"The Directory Service consistency checker has determined that either
(a)
there is not enough physical connectivity published via the Active
Directory
Sites and Services Manager to create a spanning tree connecting all the
sites
containing the Partition DC=authentify,DC=inc, or (b) replication
cannot
be
performed with one or more critical servers in order for changes to
propagate
across all sites (most often due to the servers being unreachable).
For (a), please use the Active Directory Sites and Services Manager to
do
one of the following:
1. Publish sufficient site connectivity information such that the
system
can
infer a route by which this Partition can reach this site. This option
is
preferred.
2. Add an ntdsConnection object to a Domain Controller that contains
the
Partition DC=authentify,DC=inc in this site from a Domain Controller
that
contains the same Partition in another site.
For (b), please see previous events logged by the NTDS KCC source that
identify the servers that could not be contacted. "
Now when I run repadmin /showism on Site D's domain controller (the one
giving me the errors) I get:
==== TRANSPORT CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=authe
ntify,DC=inc CONNECTIVITY INFORMATION FOR 4 SITES: ====
0, 1, 2, 3
( 0) CN=Corp2,CN=Sites,CN=Configuration,DC=authentify,DC=inc
0:0:0, 100:45:0, 100:30:0, 100:40:0
2 server(s) are defined as bridgeheads for transport (null) & site :
, pwzTransportDn, pwzSiteDn( 0)
CN=ACHCMS02,CN=Servers,CN=Corp2,CN=Sites,CN=Conf
iguration,DC=authentify,DC=inc
2 server(s) are defined as bridgeheads for transport (null) & site :
, pwzTransportDn, pwzSiteDn( 1)
CN=ACHCDC03,CN=Servers,CN=Corp2,CN=Sites,CN=Conf
iguration,DC=authentify,DC=inc
( 1) CN=Dev1,CN=Sites,CN=Configuration,DC=authentify,DC=inc
100:45:0, 0:0:0, 200:45:0, 200:45:0
All DCs in site CN=Dev1,CN=Sites,CN=Configuration,DC=authentify,DC=inc
(with
tra
ns & hosting NC) are bridgehead candidates.
( 2) CN=Prod1,CN=Sites,CN=Configuration,DC=authentify,DC=inc
100:30:0, 200:45:0, 0:0:0, 200:40:0
All DCs in site CN=Prod1,CN=Sites,CN=Configuration,DC=authentify,DC=inc
(with tr
ans & hosting NC) are bridgehead candidates.
( 3) CN=QA1,CN=Sites,CN=Configuration,DC=authentify,DC=inc
100:40:0, 200:45:0, 200:40:0, 0:0:0
All DCs in site CN=QA1,CN=Sites,CN=Configuration,DC=authentify,DC=inc
(with
tran
s & hosting NC) are bridgehead candidates.
So Site D's domain controller CAN replicate with everyone...it's
showing
that in repadmin /showism
When I run repadmin /showreps I get:
Dev1\ACHDDC02 (Site D's Domain controller)
DSA Options : IS_GC
objectGuid : bf58ef95-9f3d-496d-bbf7-b102f475aa79
invocationID: 4fdcd78e-116f-4c3d-a1a4-aab6b41b05f5
==== INBOUND NEIGHBORS =====================================
CN=Schema,CN=Configuration,DC=authentify,DC=inc
Corp2\ACHCMS02 via RPC <Site A domain controller>
objectGuid: 52339a87-a8ae-4a74-a9ac-107507c26be8
Last attempt @ 2007-03-21 12:37.06 was successful.
CN=Configuration,DC=authentify,DC=inc
Corp2\ACHCMS02 via RPC <Site A domain controller>
objectGuid: 52339a87-a8ae-4a74-a9ac-107507c26be8
Last attempt @ 2007-03-21 12:37.06 was successful.
DC=authentify,DC=inc
Corp2\ACHCMS02 via RPC <site A domain controller>
objectGuid: 52339a87-a8ae-4a74-a9ac-107507c26be8
Last attempt @ 2007-03-21 12:37.06 was successful.
==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ===========
So as far as I can tell it's replicating...so why am I getting these
errors
in my event viewer? I am confused.....
Thanks for any help you can give me!
.
- Follow-Ups:
- Re: Replication Issues with A/D
- From: Herb Martin
- Re: Replication Issues with A/D
- References:
- Replication Issues with A/D
- From: TS_Confusion
- Re: Replication Issues with A/D
- From: Jorge de Almeida Pinto [MVP - DS]
- Re: Replication Issues with A/D
- From: TS_Confusion
- Replication Issues with A/D
- Prev by Date: Re: Can WSUS run on a domain controller running DNS and DHCP?
- Next by Date: Re: Replication Issues with A/D
- Previous by thread: Re: Replication Issues with A/D
- Next by thread: Re: Replication Issues with A/D
- Index(es):
Relevant Pages
|