DOCUMENT:Q100009  20-JUL-1993  [W_NT]
TITLE   :INF: RPC Can Use Multiple Protocols
PRODUCT :Windows NT
PROD/VER:3.10
OPER/SYS:WINDOWS
KEYWORDS:

------------------------------------------------------------------
The information in this article applies to:
 
 - Microsoft Windows NT operating system version 3.1
------------------------------------------------------------------
 
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.
 
Currently supported RPC protocols are:
 
   ncacn_dnet_nsp (DECNet)
   ncacn_ip_tcp   (TCP/IP)
   ncacn_nb_nb    (NetBIOS over NetBEUI)
   ncacn_nb_tcp   (NetBIOS over TCP)
   ncacn_np       (Named Pipes)
   ncalrpc        (LPC)
 
Note: All protocols are connection-oriented. Mailslots (or other
connectionless methods) are not supported.
 
Additional reference words: 3.10

=============================================================================

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.

Copyright Microsoft Corporation 1993.