RPC Endpoint Mapper May Register the Same Interfaces (265254)

The information in this article applies to:

Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Professional

This article was previously published under Q265254

SYMPTOMS

When Remote Procedure Call (RPC) listens on a specific network address, the full machine name is returned instead of the network address that you asked to listen.

CAUSE

When you register an RPC endpoint to an interface with the same interface/GUID of a previously-registered endpoint, the newer endpoint mapping overwrites the previous endpoint mapping. The endpoint mapper does not allow two processes to register the same interface.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix should have the following file attributes or later:

   Date      Time    Version       Size     File name
   --------------------------------------------------
   6/13/00   9:03PM  5.0.2195.2096 178,000  Rpcss.dll

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.

MORE INFORMATION

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Modification Type:	Minor	Last Reviewed:	9/26/2005
Keywords:	kbHotfixServer kbQFE kbbug kbenv kbfix kbQFE kbWin2000PreSP2Fix KB265254