When using the ncacn_spx and ncadg_ipx transports, the server name is exactly the same as the Windows NT or Windows 95 server name. However, since the names are distributed using Novell protocols, they must conform to the Novell naming conventions. If a server name is not a valid Novell name, servers will not be able to create endpoints with the ncacn_spx or ncadg_ipx transports.
A valid Novell server name contains only the characters between 0x20 and 0x7f. Lowercase characters are changed to uppercase. The following characters cannot be used:
"*,./:;<=>?[]\|]
To maintain compatibility with the first version of Windows NT, ncacn_spx and ncadg_ipx also allow you to use a special format of the server name known as the tilde name. The tilde name consists of a tilde, followed by the server's eight-digit network number, and then followed by its twelve-digit Ethernet address. Tilde names have an advantage in that they do not require any name service capabilities. Thus, if you are connected to a server, the tilde name will work.
The following tables contain two sample configurations used to illustrate the points previously described:
| Component | Configured As |
|---|---|
| Windows NT or Windows 95 Server | NWCS |
| Windows NT or Windows 95 Client | NWCS |
| Windows 3.x/MS-DOS Client | NetWare Redirector |
The configuration in the previous table requires that you have NetWare file servers or routers on your network. It will produce the best performance because the server names are stored in the NetWare Bindery.
| Component | Configured As |
|---|---|
| Windows NT or Windows 95 Server | SAP Agent |
| Windows NT or Windows 95 Client | IPX/SPX |
| Windows 3.x/MS-DOS Client | IPX/SPX |
The second configuration works in an environment that does not contain NetWare file servers or routers (for example, a network of two computers: a Windows NT server and an MS-DOS client). Name resolution, which is accomplished during the first call over a binding handle, will be slightly slower than the first configuration. In addition, the second configuration results in more traffic generated over the network.
To implement name resolution, when an RPC server uses an SPX or IPX endpoint, the server name and endpoint are registered as a SAP server of type 640 (hexadecimal). To resolve a server name, the RPC client sends a SAP request for all services of the same type, and then scans the list of responses for the name of the server. This process occurs during the first RPC call over each binding handle. For additional information on the SAP protocol for Novell, see your NetWare documentation.
Note The 16-bit Windows client applications that use the ncacn_spx or ncadg_ipx transports 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.