endpoint

endpoint( protocol-sequence:[endpoint-port]  [ , ...] )

protocol-sequence

Specifies 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_tcpH_YP54

Connection-oriented NetBIOS over TCP

Client and server: Windows NT
Client only: MS-DOS, Windows 3.x 

ncacn_nb_ipxH_YEB.

Connection-oriented NetBIOS over IPX

Client and server: Windows NT
Client : MS-DOS, Windows 3.x

ncacn_nb_nbGLLC0H

Connection-oriented NetBEUI

Client and server: Windows NT, Windows  95
Client : MS-DOS, Windows 3.x

ncacn_ip_tcpCKYP54

Connection-oriented TCP/IP

Client and server: Windows 95 and Windows NT
Client: MS-DOS,Windows 3.x, and Apple  Macintosh 

ncacn_npV3FZNR

Connection-oriented named pipes

Client and server: Windows NT
Client: MS-DOS, Windows 3.x, Windows 95

ncacn_spxNLLAWD

Connection-oriented SPX

Client and server: Windows NT, Windows 95
Client: MS-DOS, Windows 3.x

ncacn_dnet_nsp11HJU6_

Connection-oriented DECnet

Client only: MS-DOS, Windows 3.x

ncacn_at_dsp510W_.N

Connection-oriented AppleTalk DSP

Server: Windows NT
Client: Apple Macintosh

ncacn_vns_spp3A89XOP

Connection-oriented Vines SPP

Client and server: Windows NT
Client: MS-DOS, Windows 3.x

ncadg_ip_udpUFYB4

Datagram (connectionless) UDP/IP

Client and server: Windows NT
Client: MS-DOS, Windows 3.x

ncadg_ipxOEL7WD

Datagram (connectionless) IPX

Client and server: Windows NT
Client: MS-DOS, Windows 3.x

ncalrpcXZ13RF

Local procedure call

Client and server: Windows NT and Windows 95

 

endpoint-port

Specifies a string that represents the endpoint designation for the specified protocol family. The syntax of the port string is specific to each protocol sequence.

 

Examples

endpoint("ncacn_np:[\\pipe\\rainier]")

 

endpoint("ncacn_ip_tcp:[1044]", "ncacn_np:[\\pipe\\shasta]")

 

Remarks

The endpoint attribute specifies a well-known port or ports (communication endpoints) on which servers of the interface listen for calls.

The endpoint specifies a transport family such as the TCP/IP connection-oriented protocol, a NetBIOS connection-oriented protocol, or the named-pipe connection-oriented protocol.

The protocol-sequence value determines the valid values for the endpoint-port. The MIDL compiler checks only general syntax for the endpoint-port entry. Port specification errors are reported by the run-time libraries. For information about the allowed values for each protocol sequence, see the topic for that protocol sequence.

The following protocol sequences specified by DCE are not supported by the MIDL compiler provided with Microsoft RPC: ncacn_osi_dna and ncadg_dds.

Make sure that you correctly quote backslash characters in endpoints. This error commonly occurs when the endpoint is a named pipe. Endpoint information specified in the IDL file is used by the RPC run-time functions RpcServerUseProtseqIfF93DMZ and RpcServerUseAllProtseqsIfE_92SC. 

See Also

IDL