Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

From the beginning, I've heard that you never, ever disable the Remote Procedure Call service in Windows. This leads to horrible things that used to be hard to overturn (I believe that it's no longer easy to do but is now much easier to fix). However, I have no idea what it does or why it is so important to basically the entire operating system.

Is it possible to sum up the purpose of the RPC service and why so many other services/applications/operations depend on it to run?

share|improve this question

2 Answers 2

Remote Procedure Call (RPC)

source: http://searchsoa.techtarget.com/definition/Remote-Procedure-Call

Remote Procedure Call (RPC) is a protocol that one program can use to request a service from a program located in another computer in a network without having to understand network details. (A procedure call is also sometimes known as a function call or a subroutine call.) RPC uses the client/server model. The requesting program is a client and the service-providing program is the server. Like a regular or local procedure call, an RPC is a synchronous operation requiring the requesting program to be suspended until the results of the remote procedure are returned. However, the use of lightweight processes or threads that share the same address space allows multiple RPCs to be performed concurrently.

When program statements that use RPC are compiled into an executable program, a stub is included in the compiled code that acts as the representative of the remote procedure code. When the program is run and the procedure call is issued, the stub receives the request and forwards it to a client runtime program in the local computer. The client runtime program has the knowledge of how to address the remote computer and server application and sends the message across the network that requests the remote procedure. Similarly, the server includes a runtime program and stub that interface with the remote procedure itself. Results are returned the same way.

There are several RPC models and implementations. A popular model and implementation is the Open Software Foundation's Distributed Computing Environment (DCE). The Institute of Electrical and Electronics Engineers defines RPC in its ISO Remote Procedure Call Specification, ISO/IEC CD 11578 N6561, ISO/IEC, November 1991.

RPC spans the Transport layer and the Application layer in the Open Systems Interconnection (OSI) model of network communication. RPC makes it easier to develop an application that includes multiple programs distributed in a network.

Alternative methods for client/server communication include message queueing and IBM's Advanced Program-to-Program Communication (APPC).


Here more from Microsoft:http://msdn.microsoft.com/en-us/library/windows/desktop/aa378651(v=vs.85).aspx

Purpose
Microsoft Remote Procedure Call (RPC) defines a powerful technology for creating distributed client/server programs. The RPC run-time stubs and libraries manage most of the processes relating to network protocols and communication. This enables you to focus on the details of the application rather than the details of the network.
Where applicable
RPC can be used in all client/server applications based on Windows operating systems. It can also be used to create client and server programs for heterogeneous network environments that include such operating systems as Unix and Apple.

share|improve this answer

The designers of Windows decided to make many things talk to each other over RPC - so that they can talk either locally or over a network.

This includes things like Active Directory, most MMC consoles, the functionality of some control panel applets like Device Manager, many of the things in Administrative Tools, and possibly internal Windows components.

I believe even when you are accessing an MMC console, like compmgmt.msc to view things about the local machine, it's basically RPC'ing to localhost (I could be wrong though).

Think of RPC as something one level above TCP/IP that's used as a low-level (and insecure) networkable communications framework by many Windows components. Why not use TCP/IP directly? At the time Windows NT was engineered (initial version released in 1993), you had other network protocols besides TCP/IP in common use, such as Netware (SPX/IPX), NetBIOS, AppleTalk (I think Windows supported this back in the day, could be wrong ...) and such. So this is a network-agnostic way for Windows components to be able to talk to other components on the local machine or remote machine.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.