The source server is currently rejecting replication requests.

"The source server is currently rejecting replication requests."

I have secondary DC crash, after I restore data from image backup, and the I
tried to replicate dirctory. I got the following error:

Source: Default-First-Site-Name\PrimaryServer
******* 35 CONSECUTIVE FAILURES since 2007-05-31 15:47:35
Last error: 8456 (0x2108):
The source server is currently rejecting replication requests.

Does anyone know how to fix the problem?

I aslo get the folllowing error inforamtion:

C:\Program Files\Support Tools>repadmin /showvector /latency DNname
Caching GUIDs.
...
DsReplicaGetInfo() failed with status 8453 (0x2105):
Replication access was denied.

Restoring DCs from imaging ISN'T a supported method of AD restoration....
http://support.microsoft.com/kb/885875

Thank you for your response. Is there any easy to do this. There are a lot
of work when I read "recovering from a USN rollback in Winows Server 2003".
Is there another way to fix this problem such as changing register entry?

I have another question, if the image backup is a not good backup software
for AD, what software is the best for AD? Can I use backup software form
Windows Accessaries?

You can use Windows NTBackup or any Active Directory-aware backup and
restoration utility supported method, check that with your vendor backup
software.
- Disconnect the Failed Dc from network.
- Force Demotion on that Server (dcpromo /forceremoval)
- Then remove all references to that Dc on AD database (Metadata cleanup).
- Remove any Dns references to the Dc.
- If necessary seize any left Op Master roles that were hosted by that Dc.
- If the domain controller that you are demoting is a DNS server or global
catalog server, you must create a new GC or DNS server to satisfy load
balancing, fault tolerance, and configuration settings in the forest.
- When you use the remove selected server command in NTDSUTIL, the NTDSDSA
object, the parent object for incoming connections to the domain controller
that you forcibly demoted is removed. The command does not remove the parent
server objects that appear in the Sites and Services snap-in. Use the Active
Directory Sites and Services MMC snap-in to remove the server object if the
domain controller will not be promoted into the forest with the same
computer name
Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller
http://support.microsoft.com/kb/255504/
Wizard to force demotion in Windows Server 2003 and in Windows 2000 Server
http://support.microsoft.com/kb/332199
How to remove data in Active Directory after an unsuccessful domain
controller demotion
http://support.microsoft.com/?kbid=216498
Clean up server metadata
http://technet2.microsoft.com/Window....mspx?mfr=true

I got problem when I performed the metadata cleanup. The error message is as
follows:

C:\Documents and Settings\Administrator>ntdsutil
ntdsutil: metadata cleanup
metadata cleanup: connections
server connections: connect to server server2.gov.local
Binding to server2.gov.local ...
DsBindW error 0x6d9(There are no more endpoints available from the endpoint
mapp
er.)
server connections: connect to server server2
Binding to tsprott ...
DsBindW error 0x6d9(There are no more endpoints available from the endpoint
mapp
er.)
server connections: quit
metadata cleanup: quit
ntdsutil: quit

C:\Documents and Settings\Administrator>

I have read the article: http://support.microsoft.com/default.aspx/kb/839880
and verfied each steps. However, I still got the error. What should I do?
Please help me out.

Thank you for your help. I did fixed the Secondary DCs. I didn't performed
the metadta cleanup since that error. However, I did all other cleanup. I
removed the records in the PDC and joined the domain again. Then, I ran
dcpromo command. It works fine after I checked all event log, as well as
replication correct. Therefore, both DCs work propably.

Don't forguet to run dcdiag and net diag and search if you have any output
errors.

[danfox44]

I had a similar issue on a Windows 2003 server which also doubled as an Exchange server - I used Acronis to move the O/S from old failing hardware to new hardware and in doing so broke replication. When trying to replicate I got the error: "The source server is currently rejecting replication requests" I also got the same error when trying to run dcpromo.

dcpromo /forceremoval was not an option for me since it would orphan my Exchange server. I could have moved all mailboxes then forced demotion but chose to call microsoft support hoping there was a trick to fix this issue since the server was now in good physical shape and all services were functioning however because the GUID changed AD picked up on the Acronis Image I preformed and assumed a USN rollback scenario.

Microsoft support did have a solution for me and ran the following commands which then allowed my server to replicate data again.

Please keep in mind this worked for me because all i had done was change my server hardware via Acronis (like Ghost) and did not have any other issues beyond replication.

enabling in bound replication - ran at command prompt of orphaned domain controller

repadmin /options servername - disable_inbound_repl
=========================================
enabling outbound replication

repadmin /options servername - disable_outbound_repl
======================================

[pat@synergyit.ca]

I had the same issue. Enabling replications as mentioned here helped me to resolve it.

http://technet.microsoft.com/en-us/l...8WS.10%29.aspx


Thanks a lot