RPC Endpoint Mapper Will Not Register All Interfaces Using DCE rpc_ep_register
This article was previously published under Q188879
This article has been archived. It is offered "as is" and will no longer be updated.
When an RPC application uses DCE rpc_ep_register to register endpoints, aWindows NT 4.0 computer will only register endpoints on a single adapterinto the system's local endpoint map.
The Microsoft RPC Endpoint Mapper did not store the adapter IP address aspart of the Endpoint Database.
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 theMicrosoft 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 applyingthis fix. This hotfix is dependent on an earlier hotfix to Ole32.dll, andrequires a version of Ole32.dll dated no earlier than 3/24/98. Ole32.dllis supplied along with RPCSS in this hotfix.
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.
Article ID: 188879 - Last Review: 10/09/2013 17:45:54 - Revision: 1.3
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
- kbnosurvey kbarchive kbhotfixserver kbqfe kbapi kbbug kbfix kbnetwork kbqfe kbrpc KB188879