Error 1722 The Rpc Server Is Unavailable Server 2003
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered error 1722 the rpc server is unavailable rightfax by: The RPC server is unavailable.(Error 1722) Windows Server > error 1722 the rpc server is unavailable windows 2008 r2 Directory Services Question 0 Sign in to vote When m running repadmin /showrepl ad1* /verbose /all
Error 1722 The Rpc Server Is Unavailable Dameware
/intersite for replication then it shows following error CN=Configuration,DC=fitnessonrequest,DC=com FOR\ADCENTER1 via RPC DSA object GUID: e4d865bc-0168-4a54-8ee2-90545560f916 Address: e4d865bc-0168-4a54-8ee2-90545560f916._msdcs.fitnessonrequest.com DSA invocationID: 25af071a-3c79-4b64-bc5f-68d88b744ea4 https://technet.microsoft.com/en-us/library/replication-error-1722-the-rpc-server-is-unavailable(v=ws.10).aspx DO_SCHEDULED_SYNCS WRITEABLE COMPRESS_CHANGES NO_CHANGE_NOTIFICATIONS USNs: 5103995/OU, 5103995/PU Last attempt @ 2011-11-23 05:26:27 failed, result 1722 (0x6ba): The RPC server is unavailable. 198 consecutive failure(s). Last success @ 2011-11-21 06:03:45. any one can say what could i do even all settings are fineSharad Singh | My blogs: SharadTech https://social.technet.microsoft.com/Forums/windows/en-US/8b62cd08-65c1-49e7-9919-881f6ff5a105/the-rpc-server-is-unavailableerror-1722?forum=winserverDS | Twitter: @MrLucknowWale | Wednesday, November 23, 2011 11:36 AM Reply | Quote Answers 0 Sign in to vote The error " The RPC server is unavailable" relates to network connectivity or port being blocked on the firewall. verify the network connectivity first and then ports on the firewall. For ports you can use portquery tool which can be downloaded for free and can be installed on the server. http://blogs.technet.com/b/abizerh/archive/2009/06/11/troubleshooting-rpc-server-is-unavailable-error-reported-in-failing-ad-replication-scenario.aspx Regards Awinish Vishwakarma MY BLOG: awinish.wordpress.comThis posting is provided AS-IS with no warranties/guarantees and confers no rights. Marked as answer by Elytis ChengModerator Thursday, December 01, 2011 8:43 AM Wednesday, November 23, 2011 12:33 PM Reply | Quote Moderator 0 Sign in to vote Most likely there is a firewall that is blocking high ports between the two dc's. I have an article on firewall Ports needed for Replication with a couple of quick troubleshooting tips at: http://www.pbbergs.com/windows/articles.htm -- Paul Bergson MVP - Directory Services
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about http://serverfault.com/questions/207000/the-rpc-server-is-unavailable-when-replicating-domain-controllers Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and http://windowsitpro.com/networking/troubleshoot-ad-replication network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top “The error 1722 RPC Server is unavailable” when replicating domain controllers up vote 1 down vote favorite I have two domain controllers: DC1: Win2k3 R2 EGDC1: Win2k8 R2 When I try to replicate these two (via Manage Sites and Services and under NTDS Settings) by selecting Replicate Now, I get the error message The RPC Server is unavailable. It doesn't matter if I try this while remoted into DC1 or DC2. According to this technet error 1722 the article, this is a problem with a machine being down. However, I can additionally have both domain controllers ping one another just fine so there is no DNS issue nor any connectivity issue. Both are on the same LAN and even on the same subnet, so no VPN/wifi/firewall/quirky issues like that should be a problem. Additionally, I verified that the RPC service is running on both boxes. What could the problem be and how would I fix it? dcdiag results: Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = EGDC1 * Identified AD Forest. Ldap search capabality attribute search failed on server DC1, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Done gathering initial info. Doing initial required tests Testing server: INF\EGDC1 Starting test: Connectivity ......................... EGDC1 passed test Connectivity Doing primary tests Testing server: INF\EGDC1 Starting test: Advertising ......................... EGDC1 passed test Advertising Starting test: FrsEvent ......................... EGDC1 passed test FrsEvent Starting test: DFSREvent ......................... EGDC1 passed test DFSREvent Starting test: SysVolCheck ......................... EGDC1 passed test SysVolCheck Starting test: KccEvent ......................... EGDC1 passed test KccEvent Starting test: KnowsOfRoleHolders [DC1] DsBindWithSpnEx() failed with erro
WindowsWindows 10 Windows Server 2012 Windows Server 2008 Windows Server 2003 Windows 8 Windows 7 Windows Vista Windows XP Exchange ServerExchange Server 2013 Exchange Server 2010 Exchange Server 2007 Exchange Server 2003 Outlook Unified Communications/Lync SharePoint Virtualization Cloud Systems ManagementSystem Center PowerShell & Scripting Active Directory & Group Policy Mobile Networking Storage TrainingOnline Training IT/Dev Connections Webcasts VIP Library Digital Magazine Archives InfoCentersIT Innovators Mobile Computing Business Now Desktop VDI All About Converged Architecture Advertisement Home > Systems Management > Networking > Troubleshoot AD Replication Troubleshoot AD Replication Magic wand not required May 29, 2007 Sean Deuby | Windows IT Pro EMAIL Tweet Comments 7 Advertisement Web Abstract: Troubleshoot Microsoft Active Directory (AD) replication. Verify that the target Microsoft Active Directory (AD) domain controller’s (DC’s) operating system (OS) and directory service are working properly. Verify that the Domain Name System (DNS) directory service is working properly on both the target and source Microsoft Active Directory (AD) domain controllers (DCs). Verify that the target Microsoft Active Directory (AD) domain controller (DC) can resolve the source Microsoft Active Directory (AD) domain controller (DC). Check the Kerberos authentication protocol and the services Kerberos depends on. Check firewall configurations, because some firewall configuration changes might block replication. Active Directory (AD) replication is the method by which directory changes made at one domain controller (DC) pass to other DCs. AD is a very robust and fault-tolerant service. Because AD is distributed across many DCs, losing parts of the whole doesn't cripple the overall directory service. In an AD forest you must monitor not only the DCs' basic health but also replication between the DCs. In my experience, replication in an unmonitored forest tends to fall apart over time, even if you configured the DCs carefully. Monitoring and repairing replication problems when they occur is much easier than fixing a forest with accumulated problems. But regardless of whether or not you monitor your AD replication, you'll inevitably need to troubleshoot it. In this article I explain some basic replication principles, and I present a straightforward methodology for troubleshooting AD replication problems. AD replication trou