Unable to Prevent RPC from Binding to an Interface
This article was previously published under Q229702
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
By default, the RPC Endpoint Mapper binds to all interfaces on a computer running Windows NT. To prevent the RPC Endpoint Mapper from binding to all interfaces, you must apply the following hotfix and create the registry entry below.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
- Start Registry Editor (Regedt32.exe).
- Go to the following key:Hkey_Local_Machine\System\CurrentControlSet\Services\RPCSS
- On the Edit menu, click Add, and then type:
ListenOnInternetIf this value is set to "Y", the RPCSS listens on all ports. If the value is set to "N", RPCSS listens based on the current policy.
- http://www.microsoft.com/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ -or-
- 152734 how to obtain the latest windows nt 4.0 service pack
Microsoft has confirmed that this is a problem in Windows NT 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 5.
Article ID: 229702 - Last Review: 11/02/2013 23:07:00 - Revision: 3.0
Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition
- kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB229702