How to Set Up a Default RPC Name Server

Last reviewed: January 20, 1996
Article ID: Q142041
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5 and 3.51
  • Microsoft Windows NT Server versions 3.5 and 3.51

SUMMARY

The Windows NT Remote Procedure Call (RPC) mechanism uses a distributed architecture for the name service by default. When an RPC client starts, it attempts to locate the RPC server in the following order:

  • Local computer
  • Primary domain controller (PDC)
  • Backup domain controller (BDC)
  • Broadcasts to the workgroup or domain using mailslots (\MailSlot\RpcLoc_s)

This process consumes a lot of time. This article describes how to specify a computer on the network as the default RPC name server.

MORE INFORMATION

To specify a Windows NT Server as the default RPC name server, do the following in the registry of the Windows NT workstation:

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

  1. Run Registry Editor (Regedt32.exe).

  2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:

    Software\Microsoft\RPC\NameService

  3. Change the values to the following:

    Value Name: NetworkAddress Data Type: REG_SZ String: <Server name>

    Value Name: ServerNetworkAddress Data Type: REG_SZ String: <Server name>

  4. Choose OK, and quit Registry Editor.


Additional reference words: prodnt 3.50 3.51 api
KBCategory: kbnetwork kbhowto
KBSubcategory: ntnetserv ntconfig


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 20, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.