Dsgetdcname Call Failed Error 1722
Contents |
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server warning dcgetdcname gc_server_required call failed error 1722 and Tools Blogs TechNet Blogs TechNet Flash Newsletter TechNet dcdiag a recent replication attempt failed Gallery TechNet Library TechNet Magazine TechNet Subscriptions TechNet Video TechNet Wiki Windows Sysinternals Virtual
Dsgetdcname Call Failed Error 1355
Labs Solutions Networking Cloud and Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center
Dsgetdcname Call Failed Error 1355 The Locator Could Not Find The Server
2012 R2 Microsoft SQL Server 2014 SP1 Windows 8.1 Enterprise See all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 1722 the rpc server is unavailable domain controller 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Troubleshooting Troubleshooting Active Directory Domain Services Troubleshooting Active Directory Replication Problems Troubleshooting Active Directory Replication Problems Replication error 1722 The RPC s
on the OS configuration specific to a Domain Controller, rather than the Directory Service itself, but I thought this was still the best place for my question I have a 2008
Error 1722 The Rpc Server Is Unavailable Windows 2012
forest with a root domain and 4 child domains, 53 DC's in total over error 1722 the rpc server is unavailable windows 7 multiple sites. I ran a DCDIAG /c /e from a DC in the root domain, and +40 of the DC's returned windows was unable to open service control manager database error 1722 the following errors: Starting test: Advertising Fatal Error:DsGetDcName (DCName) call failed, error 1722 The Locator could not find the server. DCName failed test Advertising Starting test: MachineAccount Could not open pipe with [DCName]:failed with 53 https://technet.microsoft.com/en-us/library/replication-error-1722-the-rpc-server-is-unavailable(v=ws.10).aspx The network path was not found. Could not get NetBIOSDomainName Failed can not test for HOST SPN Failed can not test for HOST SPN DCName passed test MachineAccount Starting test: NCSecDesc Ldap search capability attribute search failed on server DCName, return value = 81 DCName failed test NCSecDesc Starting test: NetLogons [DCName] An net use or LsaPolicy operation failed with error 53, The network path was not found..: DCName failed test http://www.networksteve.com/enterprise/topic.php/DCDIAG_fails_with:_call_failed,_error_1722,_Could_not_open_pipe/?TopicId=85753&Posts=18 NetLogons" I did some testing and worked out DC's that passed these tests were either in the same domain or the same site as the source DC. Conclusion; it was resolving the DNS name in the former and doing a broadcast lookup for DC's in the same site for the latter. Therefore all DC's in child domains and not in the same site failed the tests listed above. Therefore my question is; is this normal, should I just expect a dcdiag /e to fail in a multi-domain forest? How would you normally configure DNS or the OS of the DC to resolve this? Do people normally change the network properties to append DNS suffixes for all the domains/is it okay to append the DNS suffixes, or will this cause issues on the DC? May 14th, 2015 9:01am Hi, Have you done any migration of DC's also Can you provide the output of following command. Repadmin /replsum /errorsonly Free Windows Admin Tool Kit Click here and download it now May 14th, 2015 9:23am Hi First;error 1722 seems like there is connectivity issue, -Have you checked the Firewall ports&Connectivity? - Do you install AV on dc's,if yes check the AV logs.Also disbale AV and test. check these articles also; https://technet.microsoft.com/en-us/library/replication-error-1722-the-rpc-server-is-unavaible%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396 http://blogs.technet.com/askds/archive/2011/03/22/what-does-dcdiag-
How to break the AD tools with incorrect NICsettings Posted on 03/31/2012 by jasonsherry I spent a few hours today trying to figure out https://blog.jasonsherry.net/2012/03/31/how-to-break-the-ad-tools-with-incorrect-nic-settings/ why the AD tools (AD Users & Computer, AD Sites & Services, etc) were not working on an Exchange 2010 server, running on Windows 2008 R2, today. The odd thing http://www.chicagotech.net/netforums/viewtopic.php?f=3&t=15214 was that Exchange was working fine but the following errors were being generated in the Application log about every five minutes. Event ID: 6003 Source: MSExchange SACL Watcher SACL Watcher servicelet error 1722 encountered an error while monitoring SACL change. Got error 1722 opening group policy on system wfsad02.company.local in domain company. DCDIAG was also failing on multiple tests, see “DCDIAG results” at the end of this post. The odd thing was that DCDIAG test were working fine against DC outside of the AD Site the Exchange server was in. After running multiple tests call failed error from different servers this server was the only one having these issues. So I then decided to check some NIC settings and discovered the issue: The above settings would be OK if this NIC was being used for iSCSI communications. But for client traffic ALL of the above should be checked\enabled. For DAG replication traffic TCP/IPv4, TCP/IPv6, and the two Link-Layer options should also be checked. So to break the AD tools and cause DCDIAG errors just uncheck these options. After doing this you won’t find much help searching for the errors as I found out. So I wrote this post to hopefully help others who have a misconfigured NIC on a Windows server. DCDIAG results Testing server: WFS\WFSAD01 Starting test: Advertising Fatal Error:DsGetDcName (WFSAD01) call failed, error 1722 The Locator could not find the server. ……………………. WFSAD01 failed test Advertising Starting test: SysVolCheck [WFSAD01] An net use or LsaPolicy operation failed with error 1231, The network location cannot be reached. For information about network troubleshooting, see Windows Help.. ……………………. WFSAD01 failed test SysVolCheck Starting test: MachineAccount Could not open