Replication intersite troubles

  • Thread starter Thread starter Rostislav Nedosekin
  • Start date Start date
R

Rostislav Nedosekin

Hello all.
Please give me an advice to solve the problem. Searching
KB's didn't help.
Situation:
We have W2003 domain company.com. We had another NT4
domian dom1 which was standalone domain with trust
relation ships with company.com. Domain dom1 had 2 domain
controllers. We upgaded PDC NTDC00 to W2000 domain
controller and while upgrade process joined dom1 domain as
a child to domain company.com. Than we setup and promoted
additional Windows 2000 DC for dom1.company.com domain and
transfered all FSMO roles to it. The old PDC NTDC00 which
was upgraded from NT4 to W2000 was demoted because of old
hardware.
Domains company.com and dom1.company.com are in different
sites.
On the site of dom1.company.com in Active Directory Sites
and Services we see only new W2000 domain controller.
It has NTDS settings and replica link to Company.com
domain controller and it successfully replicated changes
from company.com domain.
On the site of Company.com in Active Directory Sites and
Services for dom1 site we see that there is only one
Server in that site, and it is NTDC00 without any NTDS
settings container inside. This site does not know
anything about new server. And it is impossible to
replicate changes from dom1.company.com domain.
If in Active Directory Sites and Services we connect to
new DC in Dom1.company.com domain and create replication
link froma dom1.company.com new DC to company.com DC link
is created, but if we try manually replicate changed using
this link there is error occured: "The naming context is
in the process of being removed or is not replicated from
the specified server". Dcdiag says ok, repadmin /showreps
says ok....
 
It sounds like the new DC never completed its repliation. You will see that
same error message when trying to replicate with a new DC that has not
completed a full sync.
Focus on getting the dom1.company.com DC to fully replicate with the
company.com domain. When that is completed the KCC should elect this new
dom1 DC as the bridgehead master for its site and a new replication topology
should be created.
Is Dcdiag and repadmin showing ok on both sides?
does the repadmin show the links for all partitions from company.com to
dom1.company.com?
 
Hello again.
The dom1.company.com successfully created inbound conections from
company.com domain and susccessfully replicates schema, configuration etc.
But compnay.com domain recieves no information about dom1.company.com domain.
It seems to me now, that when we promoted new dc in dom1.company.com domain
and then demoted old NTDC00 dc the information about new dc did not
replicated to company.com domain and after demoted there is no way to inform
that there is new dc.
As I wrote in first post. If I bind to new dc in dom1.company.com with
Active Directory Sites and Services we can see servers in both sites in
dom1.company.com (let in be site2) and in company.com (site1). I create new
replication link to replicate chages from site2 to site1, and when trying to
manually replicate changes, the snap in says that "The naming context is in
the process of remove or had not replicated yet". When I run repadmin
/showreps on new dc in dom1.company.com it says ok to everything, but there
is no outbound connection to site1. By the way - why? Where does repadmin
gets informations? Looks like in takes information from DC of company.com
which has no iformation about links between sites.

At first time I did not write the full topology. I kindly ask you to read it
and advice something.
In addition to company.com and dom1.company.com domains we alse have
dom2.company.com domain, which is also child to copmany.com, it healthy and
fully replicated.
So KCC on new DC in dom1.company.com automatically generates replication
link from on of DC of dom2.company.com domain. The replmon says the reason is
that DC in dom2.company.com domain is the neighbor in ring. But replication
from dc of dom2.company.com cannot be completed, couse of error 1265.
Replication access denied.
repadmin /showreps doesn't see this connection, so no erros shown
dcdiag passes all test exepting KCC, where it shows the same error as in
eventlog.
.....
No ideas where to begin.



[email protected] said:
It sounds like the new DC never completed its repliation. You will see that
same error message when trying to replicate with a new DC that has not
completed a full sync.
Focus on getting the dom1.company.com DC to fully replicate with the
company.com domain. When that is completed the KCC should elect this new
dom1 DC as the bridgehead master for its site and a new replication topology
should be created.
Is Dcdiag and repadmin showing ok on both sides?
does the repadmin show the links for all partitions from company.com to
dom1.company.com?


--
James Brandt [MSFT]


Rostislav Nedosekin said:
Hello all.
Please give me an advice to solve the problem. Searching
KB's didn't help.
Situation:
We have W2003 domain company.com. We had another NT4
domian dom1 which was standalone domain with trust
relation ships with company.com. Domain dom1 had 2 domain
controllers. We upgaded PDC NTDC00 to W2000 domain
controller and while upgrade process joined dom1 domain as
a child to domain company.com. Than we setup and promoted
additional Windows 2000 DC for dom1.company.com domain and
transfered all FSMO roles to it. The old PDC NTDC00 which
was upgraded from NT4 to W2000 was demoted because of old
hardware.
Domains company.com and dom1.company.com are in different
sites.
On the site of dom1.company.com in Active Directory Sites
and Services we see only new W2000 domain controller.
It has NTDS settings and replica link to Company.com
domain controller and it successfully replicated changes
from company.com domain.
On the site of Company.com in Active Directory Sites and
Services for dom1 site we see that there is only one
Server in that site, and it is NTDC00 without any NTDS
settings container inside. This site does not know
anything about new server. And it is impossible to
replicate changes from dom1.company.com domain.
If in Active Directory Sites and Services we connect to
new DC in Dom1.company.com domain and create replication
link froma dom1.company.com new DC to company.com DC link
is created, but if we try manually replicate changed using
this link there is error occured: "The naming context is
in the process of being removed or is not replicated from
the specified server". Dcdiag says ok, repadmin /showreps
says ok....
Click to expand...
Click to expand...
 
I think you are correct the new DC in dom1 did not complete its replication
to the root domain. Since the DC will receive replication from the root
domain, you should look there to see if the DC even shows in sites and
services on the root DCs. The domain should still exist because the DC you
demoted would not delete teh domain since it knew of the second DC.
If that DC doesn't show up in the root domain, I guess you could try to
manually add it in the configuration container. My guess would be that the
domain would have to be rebuilt.

--
James Brandt [MSFT]


Rostislav Nedosekin said:
Hello again.
The dom1.company.com successfully created inbound conections from
company.com domain and susccessfully replicates schema, configuration etc.
But compnay.com domain recieves no information about dom1.company.com
domain.
It seems to me now, that when we promoted new dc in dom1.company.com
domain
and then demoted old NTDC00 dc the information about new dc did not
replicated to company.com domain and after demoted there is no way to
inform
that there is new dc.
As I wrote in first post. If I bind to new dc in dom1.company.com with
Active Directory Sites and Services we can see servers in both sites in
dom1.company.com (let in be site2) and in company.com (site1). I create
new
replication link to replicate chages from site2 to site1, and when trying
to
manually replicate changes, the snap in says that "The naming context is
in
the process of remove or had not replicated yet". When I run repadmin
/showreps on new dc in dom1.company.com it says ok to everything, but
there
is no outbound connection to site1. By the way - why? Where does repadmin
gets informations? Looks like in takes information from DC of company.com
which has no iformation about links between sites.

At first time I did not write the full topology. I kindly ask you to read
it
and advice something.
In addition to company.com and dom1.company.com domains we alse have
dom2.company.com domain, which is also child to copmany.com, it healthy
and
fully replicated.
So KCC on new DC in dom1.company.com automatically generates replication
link from on of DC of dom2.company.com domain. The replmon says the reason
is
that DC in dom2.company.com domain is the neighbor in ring. But
replication
from dc of dom2.company.com cannot be completed, couse of error 1265.
Replication access denied.
repadmin /showreps doesn't see this connection, so no erros shown
dcdiag passes all test exepting KCC, where it shows the same error as in
eventlog.
....
No ideas where to begin.



[email protected] said:
It sounds like the new DC never completed its repliation. You will see
that
same error message when trying to replicate with a new DC that has not
completed a full sync.
Focus on getting the dom1.company.com DC to fully replicate with the
company.com domain. When that is completed the KCC should elect this new
dom1 DC as the bridgehead master for its site and a new replication
topology
should be created.
Is Dcdiag and repadmin showing ok on both sides?
does the repadmin show the links for all partitions from company.com to
dom1.company.com?


--
James Brandt [MSFT]


message
Hello all.
Please give me an advice to solve the problem. Searching
KB's didn't help.
Situation:
We have W2003 domain company.com. We had another NT4
domian dom1 which was standalone domain with trust
relation ships with company.com. Domain dom1 had 2 domain
controllers. We upgaded PDC NTDC00 to W2000 domain
controller and while upgrade process joined dom1 domain as
a child to domain company.com. Than we setup and promoted
additional Windows 2000 DC for dom1.company.com domain and
transfered all FSMO roles to it. The old PDC NTDC00 which
was upgraded from NT4 to W2000 was demoted because of old
hardware.
Domains company.com and dom1.company.com are in different
sites.
On the site of dom1.company.com in Active Directory Sites
and Services we see only new W2000 domain controller.
It has NTDS settings and replica link to Company.com
domain controller and it successfully replicated changes
from company.com domain.
On the site of Company.com in Active Directory Sites and
Services for dom1 site we see that there is only one
Server in that site, and it is NTDC00 without any NTDS
settings container inside. This site does not know
anything about new server. And it is impossible to
replicate changes from dom1.company.com domain.
If in Active Directory Sites and Services we connect to
new DC in Dom1.company.com domain and create replication
link froma dom1.company.com new DC to company.com DC link
is created, but if we try manually replicate changed using
this link there is error occured: "The naming context is
in the process of being removed or is not replicated from
the specified server". Dcdiag says ok, repadmin /showreps
says ok....
Click to expand...
Click to expand...
Click to expand...
 
Back
Top