RPC Endpoint Mapper Will Not Register All Interfaces Using DCE rpc_ep_register

Article translations Article translations
Article ID: 188879 - View products that this article applies to.
This article was previously published under Q188879
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

When an RPC application uses DCE rpc_ep_register to register endpoints, a Windows NT 4.0 computer will only register endpoints on a single adapter into the system's local endpoint map.

CAUSE

The Microsoft RPC Endpoint Mapper did not store the adapter IP address as part of the Endpoint Database.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

NOTE: Service Pack 3 must be applied to Windows NT 4.0 prior to applying this fix. This hotfix is dependent on an earlier hotfix to Ole32.dll, and requires a version of Ole32.dll dated no earlier than 3/24/98. Ole32.dll is supplied along with RPCSS in this hotfix.

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Properties

Article ID: 188879 - Last Review: October 9, 2013 - Revision: 1.3
APPLIES TO
  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbapi kbbug kbfix kbnetwork kbqfe kbrpc KB188879

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com