RPC Endpoint Mapper Will Not Register All Interfaces Using DCE rpc_ep_register (188879)


The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition
  • Microsoft Windows NT Workstation 4.0
  • Microsoft Windows NT Server 4.0
This article was previously published under Q188879

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.
Modification Type:MinorLast Reviewed:9/23/2005
Keywords:kbHotfixServer kbQFE kbAPI kbbug kbfix kbnetwork kbQFE kbRPC KB188879
©2004 Microsoft Corporation. All rights reserved.