That error indicates the RPC endpoint mapper is having trouble mapping the ephemeral ports (those >1024 that RPC services run on) It sounds like it could be a problem with either the build or the connectivity from the location you are joining from if it is intermittent versus a problem with you domain infrastructure.
After starting with the obvious- making sure the RPC services are running, startup depends on OS and role but RPC Service should always be started and automatic and the RPC Locator should be at least manual and you have proper network connectivity to a DC, I'd troubleshoot the offending client by first looking in the %windir%\DEBUG\netsetup.log. That has provided me the source of join problems on numerous occasions. I usually don't have to look any further. It is cumulative and will have all the domain joining attempts. It's also very cool in that it persists renames so you can get a nice little history of a problem member server or workstation. If that doesn't help, I'd work through the steps about ¾ of the way down in KB 839880 under the "How to resolve RPC Endpoint Mapper errors" heading. These 2 articles will usually work out RPC client errors.... http://support.microsoft.com/Default.aspx?id=839880 Troubleshooting RPC Endpoint Mapper errors using the Windows Server 2003 Support Tools from the product CD http://support.microsoft.com/default.aspx/kb/325930/ How to troubleshoot connectivity issues that are caused by RPC client protocol registry entries From: Owens, Michael [mailto:[email protected]] Sent: Thursday, June 11, 2009 6:26 AM To: NT System Admin Issues Subject: Error joining PC to a domain This is a random event, it doesnt happen all the time. When I join a computer to the domain, I get "There are no more endpoints available from the endpoint mapper" Everything that comes up on google doesn't seem to apply and since it is intermintant, it is hard to test.... it just leads me to believe something is set up incorrectly somehwhere. Has anyone seen this before? Thanks guys, Mike ________________________________ This message, and any response to it, may constitute a public record and thus may be publicly available to anyone who requests it in accordance with Chapter 149 of the Ohio Revised Code. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
