PROTSEQ
unsigned
char * Protseq[1];
Protseq
Points to a
character string identifying the network protocol used to communicate between
client and server.
Remarks
The protocol
sequence is a character string that represents a valid combination of an RPC protocol
(such as ncacn ), a transport protocol (such as tcp ), and a network protocol
(such as ip ). Microsoft RPC supports the following protocol sequences:
|
Protocol
sequence |
Description |
Supporting Platforms |
|
ncacn_nb_tcp |
Connection-oriented
NetBIOS over TCP |
client
only: MS-DOS, Windows 3.x |
|
ncacn_nb_ipx |
Connection-oriented
NetBIOS over IPX |
client
only: MS-DOS, Windows 3.x |
|
ncacn_nb_nb |
Connection-oriented
NetBEUI |
client
only: MS-DOS, Windows 3.x |
|
ncacn_ip_tcp |
Connection-oriented
TCP/IP |
client
only: MS-DOS,Windows 3.x, and Apple Macintosh |
|
ncacn_np |
Connection-oriented
named pipes |
client
only: MS-DOS, Windows 3.x, Windows 95 |
|
ncacn_spx |
Connection-oriented
SPX |
client
only: MS-DOS, Windows 3.x |
|
ncacn_dnet_nsp |
Connection-oriented
DECnet transport |
client only:
MS-DOS, Windows 3.x |
|
ncacn_at_dsp |
Connection-oriented
AppleTalk DSP |
client:
Apple Macintosh |
|
ncacn_vns_spp |
Connection-oriented
Vines SPP transport |
client
only: MS-DOS, Windows 3.x |
|
ncadg_ip_udp |
Datagram
(connectionless) UDP/IP |
client
only: MS-DOS, Windows 3.x |
|
ncadg_ipx |
Datagram
(connectionless) IPX |
client
only: MS-DOS, Windows 3.x |
|
ncalrpc |
Local
procedure call |
client and
server: Windows NT and Windows 95 |
A server
application can use a particular protocol sequence only when the RPC run-time
library and operating-system software support that protocol. A server chooses
to accept remote procedure calls over some or all of the supported protocol
sequences.
Several
server routines allow server applications to register protocol sequences with
the run-time library. Microsoft RPC functions that require a protocol-sequence
argument use the data type unsigned char.
A client can
use the protocol-sequence strings to construct a string binding using the RpcStringBindingCompose routine.
Note The ncalrpc protocol sequence is
supported only for 32-bit Windows applications.
The ncacn_dnet_nsp protocol sequence is
supported only for MS-DOS, and 16-bit Windows client applications. This release
of Microsoft RPC does not include support for the ncacn_dnet_nsp
protocol sequence with 32-bit client or server applications.
16-bit
Windows client applications that use the ncacn_spx or ncadg_ipx
protocol sequences require that the file NWIPXSPX.DLL be installed in order to
run under the Windows NT Windows on Windows (WOW) subsystem. Contact Novell to
obtain this file.
The ncacn_vns_spp
protocol sequence requires that Banyan s Enterprise Client For Windows NT
be installed. Contact Banyan for more information.
See Also