Hi

I have 3 Dc's on my site and at the moment i cannot get the one server(Gamma) to replcate to the PDC (Beta) When i try to force the replciation i get the following error

the following error occurred during the attempt to synchronize naming context Griffin.local from Domain Controller BETA to Domain Controller GAMMA

Error 0X800721a6

The operation will not continue

I have checked the even log on the PDC (beta) and i had a space issue which has been resolved but the replcaiton is still not occuring. -- griffinwindows ------------------------------------------------------------------------ griffinwindows's Profile: http://forums.techarena.in/members/84591.htm View this thread: http://forums.techarena.in/active-directory/1146315.htmhttp://forums.techarena.in

what about the times on the domain controllers?
i had an issue on 2 of my older servers where they lost power and came up
in january 2004 so AD refused to replicate.  it did synch time but not
before these errors started. manually replication was failing the same way
you are experiencing.  i fixed it by demoting then promoting after which it
started replicating again.

might want to look at this for more detailed explanation:

http://www.petri.co.il/forums/archive/index.php/t-1487.html



Show quoteHide quote

Sounds like you are running into a problem caused by having domain
controllers which were not replicating for more than a tombstone lifetime
interval. For more info, refer to
http://technet.microsoft.com/en-us/library/cc757610.aspx

hth
Marcin

Show quoteHide quote

Hi
I agree, sounds that your DC doesn't replicated within the tombstone
lifetime, but you should have eventlog errors saying that, don't you?

Show quoteHide quote

Hello griffinwindows,

Please run dcdiag /v and repadmin /showrepl and post the result from all
DC's. Maybe you have to install the support\tools\suptools.msi from the 2000/2003
installation disk, if not done already.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


Show quoteHide quote

griffinwindows <griffinwindows.3piefd@DoNotSpam.com>, posted the following:
Show quoteHide quoteWas either Gamma or Beta off the network for any period of time? As Marcin
stated, the error indicates one of the servers are past their tombstone
lifetime (default 60 days), and if there were mitigating issues taht you
were not aware of, they would definitely have prevented repllication.

If both DCs have been up on the network and they are failing replication, it
may a number of causes, starting with a basic DNS config issue, single label
name domain, multihomed domain controllers, incorrect subnet masks,
disjointed namespace, and many others.

Please post the following in order to give us an understanding of your
infrastructure's config, which will allow us to determine what may have been
the cause of the issue.

1. Event log error - please post the EventID# and source nane
2. Unedited ipconfig /all from both DCs and from one sample workstation.
3. dcdiag /v /fix > c:\dcdiag.txt (copy and paste the errors out of it)
4. netdiag /v /fix > c:\negtdiag.txt (copy and paste the errors out of it)

Thank you

Hi,

Post a complete dcdiag /v , ipconfig /all from both Beta and Gamma.

Isaac

Show quoteHide quote

Is this the last step we need to do?
Do Child DC's need unrestricted IP access to Root DC's?
After 2000 to 2003 upgrade sysvol is not accessable
Manually removing cert server from AD
Validation for 2000 to 2003 upgrade
DNS/DHCP problem while migrating computers using ADMT
DC fails when isolated from network
GPO Version mismatch in Sysvol
ADAM UserProxy Authentication (Which Domain Controller?)
Way to set using Active Directory, which ports for remote desktop?