RPC Endpoint Mapper Will Not Register All Interfaces Using DCE rpc_ep_register

ID: Q188879

The information in this article applies to:

Microsoft Windows NT Workstation version 4.0
Microsoft Windows NT Server version 4.0
Microsoft Windows NT Server version 4.0, Terminal Server Edition

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, please see the following article in the Microsoft Knowledge Base:

Q152734 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 this to be 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.

Keywords : kbnetwork NT4SP4Fix kbbug4.00 kbAPI kbRPC kbSDKPlatform kbfix4.00.sp4 kbGrpNet
Version : WinNT:4.0
Platform : winnt
Issue type : kbbug