How to Run Name Service API-Based RPC Apps in Windows 95

• Microsoft Win32 Software Development Kit (SDK) for Windows 95

SUMMARY

A Win32 RPC application that calls name service RPC APIs cannot run without adding or configuring certain registry entries.

MORE INFORMATION

RPC Server and client applications relying on the services of Microsoft RPC locator service fail with errors 0x6BF(1727 - A renote procedure call failed and did not execute), and 0x6E2(1762 - The name service is unavailable) on calls to RpcNsBindingExport() and RpcNsBindingImportBegin() APIs, respectively.

This is due to the fact that Windows 95 presently does not have a Microsoft RPC locator component available. For these applications to work correctly, the user must modify the Windows 95 system registry, so that these RPC calls can be redirected to the a locator service running on a Windows NT server or a Windows NT workstation.

Adding the following registry keys in the specified path solves this problem:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\NameService\DefaultSyntax REG_SZ "3"

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\NameService\Endpoint REG_SZ "\pipe\locator"

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\NameService\NetworkAddress REG_SZ "\\NTSERVER"

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\NameService\Protocol REG_SZ "ncacn_np"

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\NameService\ServerNetworkAddress REG_SZ "\\NTSERVER"

Here, NTSERVER is the computer name of the Windows NT server or workstation where the RPC locator service is already running. A Microsoft locator component is not currently available for Windows 95 because of the fact that the Microsoft locator uses named pipes to communicate, and Windows 95 does not support server-side named pipes.