When attempting to join a client to an Active Directory domain, you may receive the following error:
The following error occurred attempting to join the domain <domain>:
There are no more endpoints available from the endpoint mapper.
You may also see a red X on a domain controller when viewing it in the DNS Management console. If you run the dcdiag command-line utility to troubleshoot the issue, it will likely return one or more instances of the following:
Error 1753: There are no more endpoints available from the endpoint mapper.
Remote Procedure Call (RPC) is a mechanism that allows Windows processes to communicate with one another, either between systems across a network or within a single system. Numerous built-in Windows components utilize RPC. RPC uses dynamic ports for communication between systems, but a static port (TCP port 135) must also be used as a starting point for communication. The RPC endpoint mapper listens on this static port.
In a typical RPC session, a client contacts a server's endpoint mapper on TCP port 135 and requests the dynamic port number assigned to a particular service. The server responds with the port number that the service registered with RPC when it started, and the client then contacts the service on that port. Error 1753 represents a failure of the endpoint mapper to determine the port assigned to a particular service.
Possible causes of this error include the following:
A firewall or other security application is interfering with proper RPC port allocation.
The range of dynamic ports used by RPC has been restricted and depleted.
The specific service that the client is trying to reach is not running.
Name-resolution issues are causing the client to query the endpoint mapper on the wrong server.
The following steps may prove useful in troubleshooting this issue:
Check DNS. Verify that the client is using the correct DNS servers. All domain-joined machines must use only internal DNS servers for name resolution. If the client's DNS servers are correct, very that the records registered on those servers are correct as well. As this can be a lengthy process in a large environment, you may want to start by using the ping and nslookup commands on the client to show that the server's name is resolved to the correct IP address. If it is, the DNS records registered by the server are likely correct.
Verify that the service which the client is trying to reach (Active Directory Domain Services in the case of a domain-join operation) is running on the target server.
Verify that the Windows Firewall is disabled on domain controllers running Windows Server 2003. Later versions of Windows Server include a much-improved version of Windows Firewall that properly handles RPC dynamic port allocation, so it does not need to be disabled there. In fact, verify that the Windows Firewall service has not been stopped or disabled on domain controllers running Windows Server 2008 or later, as this can cause a variety of network issues.
Review Microsoft Knowledgebase article 839880, Troubleshooting RPC Endpoint Mapper Errors Using the Windows Server 2003 Support Tools from the Product CD. Some of the tools and steps in the article apply only to Windows Server 2003 or earlier, however.
To determine whether the RPC dynamic port range has been manually restricted, open Registry Editor (regedit.exe) and look for the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Internet
If the Internet key is present, the port range has been restricted. Within that key, look for a REG_MULTI_SZ value named Ports. Its data field will indicate which ports are available for RPC to use. To remove the restriction altogether, delete the Internet key. It may be exported prior to deletion so that it can be re-imported later if problems arise.
For general information on RPC and the Windows services that use it, see What Is RPC?
For details on the RPC communication process, see How IT Works: Troubleshooting RPC Errors and Replication error 1753: The are no more endpoints available from the endpoint mapper.
Article ID: SLN249100
Last Date Modified: 07/27/2018 10:39 AM
Thank you for your feedback.
