Microsoft KB Archive/100009

{|
 * width="100%"|

RPC Can Use Multiple Protocols
'Article ID: Q100009

Creation Date: 14-JUN-1993

Revision Date: 02-NOV-1995' The information in this article applies to:


 * Microsoft Win32 Software Development Kit (SDK) versions 3.1, 3.5, and 4.0

Microsoft Remote Procedure Call (RPC) does not rely on a single protocol. An RPC server can be written to use all available protocols on the server, and a client can be written in the same manner. Thus, the server or client does not have to know which protocols it supports explicitly.

RPC protocols supported by Windows 3.1 and 3.5 are:

ncacn_ip_tcp  (TCP/IP) ncacn_nb_nb   (NetBIOS over NetBEUI) ncacn_nb_tcp  (NetBIOS over TCP) ncacn_np      (Named Pipes) ncalrpc       (LPC) RPC protocols supported by Windows 3.5 only are: ncadg_ipx     (Datagram - IPX) ncacn_spx     (SPX) ncadg_ip_udp  (Datagram - UDP) ncacn_nb_ipx  (Netbios over IPX) RPC protocols supports by Windows 95 are: ncacan_ip_tcp ncacn_nb_nb ncacn_np ncacn_spx ncalrpc
 * }

-

"THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED 'AS IS' WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY." '' ©1997 Microsoft Corporation. All rights reserved. Legal Notices.

''

Additional reference words: 3.10 3.50 4.00 95

KBCategory: kbnetwork

KBSubcategory: NtwkRpc