When using Active Directory Users and Computers, you may see the error that states, "The specified domain either does not exist or could not be contacted." Logging on to the domain may give you an error that claims, "The system cannot log you on to this domain because the system’s computer account in its primary domain is missing or the password on that account is incorrect."When the Microsoft Outlook client tries to communicate with Exchange Server, RPC failures may give the client a misleading error such as, "Your logon information is incorrect," or "Outlook could not log on."In addition to these errors, when the RPC service is not available, you may experience other problems.For instance, you may not be able to browse the domain in My Network Places, or you may not be able to open the Group Policy snap-in.When the File Replication Service (FRS) fails, it could be the dreaded "RPC Unavailable" error at work.
2003 server to a doman controller using the Dcpromo tool can also reveal issues with RPC.If you’ve worked with Windows server platforms over the years, chances are you’ve seen remote procedure call (RPC) errors at one time or another.They tell you that the RPC server is unavailable, or that there are no more endpoints available, or provide some other cryptic warning. I will look at some common errors, various techniques you can use to identify the RPC errors you see, and discuss some solutions to solve specific problems.But before I talk about the specific RPC errors and solutions, let’s get a solid grounding in RPC terminology.RPC is an interprocess communication (IPC) method that is used by clients and servers to communicate with each other.