There is normally no need to configure clients. In this type of network, the Name Service is unavailable. For performance reasons, it is possible to set the client's registry so that it does not attempt to locate any Name Service provider.
|
NOTE |
This setting is not absolutely necessary, but it does significantly speed up the first connection phase to a given server. |
It is also possible to restrict the protocols used by RPC when accessing remote resources. This can be accomplished by creating the following registry values in the HKEY_LOCAL_MACHINE/SOFTWARE/TigerLogic/D3/CurrentVersion/Rpc/Client/ directory in registry:
|
DefaultProtocols |
Specifies the network protocols used by clients when the Name Service is not available (comma delimited string). The default value is (blank). If not specified, all installed protocols are used. |
|
UseProtocols |
List of the only protocols that can be used when the Name Service is available (comma delimited string). Speeds up connections, since the client usually has a smaller subset of protocols that the server has. The default value is (blank). |
The following are examples of protocols supported by RPC.
This list is not exhaustive:
|
ncalrpc |
Local RPC (Windows only) |
|
ncacn_nb_nb |
NetBIOS over NetBEUI |
|
ncacn_np |
Named Pipes |
|
ncacn_ip_tcp |
TCP/IP |
|
ncacn_nb_tcp |
NetBIOS over TCP |
|
ncacn_n_ipx |
NetBIOS over IPX |
|
ncacn_spx |
SPX |
See Also