"Error issuing replication: 8453 (0x2105)" when doing a repadmin /syncall

Question

Whenever I do a repadmin /syncall I get "CALLBACK MESSAGE: Error issuing replication: 8453 (0x2105):"
If I do a repadmin /syncall /P the command completes with no errors
I am running this command from the only FSMO roles holder for my domain
This is also in our hub office which all of our branch offices connect to. 
I was going to run "repadmin /syncall /e /P" to immediately replicate changes to all of our DCs, but I want to be sure this won't break anything.
I found two warnings in the following Microsoft article that worry me: 
http://technet.microsoft.com/en-us/library/cc811569(v=ws.10).aspx
"These are very powerful subcommands and should be used sparingly as they do not follow replication agreements that are in place and have the potential to cause replication storm and break Active Directory if not used properly."
for the /syncall switch:
"Use this command and the above flags cautiously or you can damage the replication system because this command does not follow replication agreements nor honor any replication restrictions such as DISABLE_INBOUND_REPL or DISABLE_OUTBOUND_REPL"
Is running this command safe or will I cause problems by doing this? I was thinking that because this is the FSMO roles holder doing a /P (push) to the other DCs from this one would be ok.
I should also add that doing a "repadmin /replicate" to any DC executes without any errors.

Answer 1

Can you post the dcdiag /q,repadmin /replsum and repadmin /syncall details of DC's to analyse the same.Please use skydive to post the log
"Error issuing replication: 8453 (0x2105):" This can either be a DNS misconfig,secure channel between DC broken,lingering object issue or network connectivity issue,necessary ports are not fully opened between locations,etc. Microsoft's PortQry tests specific
AD ports and the ephemeral ports, and the required responses from the services on the required AD ports it specifically scans for.  Here's more info on the ports that AD requires to properly communicate:
Active Directory Firewall Ports -
http://msmvps.com/blogs/acefekay/archive/2011/11/01/active-directory-firewall-ports-let-s-try-to-make-this-simple.aspx
Also, disable local windows firewall service, by default it is enabled in vista/windows 2008 and above. Check the network connectivity and latency.
Disable Windows Firewall:
http://technet.microsoft.com/en-us/library/cc766337(WS.10).aspx
Also ensure the following DNS setting on DC:
1. Each DC / DNS server points to its private IP address as primary DNS server and other remote/local DNS servers as secondary in TCP/IP properties.
2. Each DC has just one IP address and single network adapter is enabled.
3. Contact your ISP and get valid DNS IPs from them and add it in to the forwarders, Do not set public DNS server in TCP/IP setting of DC.
4. Once you are done, run "ipconfig /flushdns & ipconfig /registerdns", restart DNS and NETLOGON service each DC.
Do not put private DNS IP addresses in forwarder list.
5.Assign static IP address to DC if IP address is assigned by DHCP server to DC.It is strongly not recommended.
Hope this helps.
Best Regards,
Sandesh Dubey.
MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator |
My Blog
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.