INFO: Configuration Needed to Run RPC Apps Using IPX Protocol
ID: Q139559
|
The information in this article applies to:
-
Microsoft Win32 Software Development Kit (SDK), versions 3.5, 3.51, 4.0
SUMMARY
This article describes certain conmponents that need to be installed when
running RPC applications using the IPX/SPX protocol.
MORE INFORMATION
All the information below assumes that the IPX/SPX protocol is installed
and the 16-bit runtimes are installed where needed.
Platform Application Protocol Sequence Component needed
--------------------------------------------------------------------
Windows NT Server ncadg_ipx Client Services
for Netware(WKS) or
Gateway Services
for Netware(SVR)
Windows NT Server ncacn_spx Client Services
for Netware(WKS) or
Gateway Services
for Netware(SVR)
Windows 95 Server ncacn_spx no additional component
Windows NT Client(32-bit) ncadg_ipx SAP agent; else
use IPX addresses
(see note (2)
below) else Server
must have Gateway
Services for
Netware
Windows NT Client(32-bit) ncacn_spx as above
Windows 95 Client(32-bit) ncacn_spx Client for Novell
Netware else use
IPX addresses
(see note (2) below)
Windows NT Client(16-bit) ncadg_ipx SAP agent; else
use IPX addresses
(see note (2)
below) else Server
must have Gateway
Services for
Netware
Windows NT Client(16-bit) ncacn_spx as above
Windows 95 Client(16-bit) ncacn_spx Only way to
connect to server is
by using IPX
addresses (see note
(2) below)
NOTES:
- Windows 95 does not support ncadg_ipx.
- IPX addresses : The IPX address of the computer must be of the form
~XXXXXXXXYYYYYYYYYYYY. For example, if a computer's network address is
00006112 and its node address is 00AA0060DA28, you should use
~0000611200AA0060DA28.
Keywords : kbnetwork kbAPI kbNTOS310 kbNTOS350 kbNTOS351 kbRPC kbSDKPlatform kbWinOS95 kbWinOS311 kbGrpNet
Version :
Platform :
Issue type : kbinfo