Re: Fixing Replication Failures
- From: "Ace Fekay [MVP]" <PleaseAskMe@xxxxxxxxxxxxxx>
- Date: Wed, 13 Jun 2007 23:47:03 -0400
In news:r5-dnS52Ne920O3bnZ2dnUVZ_t2tnZ2d@xxxxxxxxxx,
Brian <wouldntulike2know> typed:
We are having occasional replication errors throughout our domain,
but one of the sites in particular seems to be a problem. Hoping for
some advice if this looks familiar to anyone.
If we get replication problems as indicated by repadmin /showrepl,
rebooting the remote DC gets things going again, but is not a great
solution and also it take a long time for the DC to come back up.
We have two local DCs both of which replicate with the remote DC. The
replication has failed with the remote and both of these DCs, but not
always at the same time (i.e. one works, one doesn't).
If I try to run a forced replication (repadmin /replicate...), I get
the following:
DsReplicaSync() failed waith status 1727 (0x6bf).
(I got no hits searching for that code on google BTW)
Pinging between the DCs works, as does browsing. I also tried the
port query tool on 135 and it works. The only other thing that seems
to fail when this is replication error occurs is that I can't remote
desktop to the remote DC from within out local LAN while this error
is occuring. However I can remote to another server within the remote
LAN and then remote from there to the DC.
The other point of interest in this is that if I run AD Sites and
Service on the remote DC, its site shows that it is trying to
replicate with every site in the company. If I correct that so it
just replicates with the local DCs, later I can look at it again and
its changed back.
Event viewer shows nothing of great value, really only errors that
there was a problem (15308).
Thanks!
Rebooting works? First thought makes me think the DC is multhomed. This will
definitely cause it as well as the Sites and Services issue, which a reboot
would temporarily fix it.
Replication problems relating to a reboot temporarily fixing it, can be
caused by numerous issues from DNS misconfigs, using ISP's DNS in ip
properties, ISP problems with the lines, etc.
For starters, can you post the folowing info please?
1. Unedited ipconfig /all from the three DCs in question, and one of your
clients.
2. The exact zone name spellng in DNS and whether updates are allowed on the
zone.
3. The AD DNS domain name as it shows up in ADUC.
4. If the SRV records exist under your zone.
5. Any errors in the Event logs on the DC under System, Replication Service
and Directory Services (post the Event ID# and source please)
6. Dcdiag /v /fix > c:\dcdiag.txt (post the dcdiag.txt as an attachment)
7. Netdiag /v /fix > c:\netdiag.txt (post the dcdiag.txt as an attachment)
8. More than one subnet?
9. Forwarder(s) configured?
10. Descrive your Site configuration and subnet associations to your Sites.
--
Regards,
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations
Having difficulty reading or finding responses to your post?
Instead of the website you're using, try using OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. Anonymous access. It's free - no username or password
required nor do you need a Newsgroup Usenet account with your ISP. It
connects directly to the Microsoft Public Newsgroups. OEx allows you
o easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject. It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164
"Quitting smoking is easy. I've done it a thousand times." - Mark Twain
.
- Follow-Ups:
- Re: Fixing Replication Failures
- From: Brian
- Re: Fixing Replication Failures
- References:
- Fixing Replication Failures
- From: Brian
- Fixing Replication Failures
- Prev by Date: Re: start over
- Next by Date: Re: ADAM - Schema Admins?
- Previous by thread: Fixing Replication Failures
- Next by thread: Re: Fixing Replication Failures
- Index(es):
Relevant Pages
|