PRB: RPC App Using Auto Handles Can't Call Remote Procedure

 Last reviewed: November 29, 1995
Article ID: Q140015
The information in this article applies to:
  • Microsoft Win32 Software Development Kit (SDK) version 3.51

SYMPTOMS

An RPC application using auto handles cannot call a remote procedure on a server that is in a different Windows NT computer domain than the client workstation's Windows NT computer domain.

STATUS

This behavior is by design.

MORE INFORMATION

The information in this article applies in the context of Microsoft locator service and the workstations participating in a Windows NT domain model.

Auto handles implicitly make use of the RPC name service calls to locate the server. The locator does a look up for the servers in the local domain only. Thus, if a server is registered in a different domain, calling the remote procedure will create an exception (typically error 1727), assuming there are no RPC servers available that expose the same interface in the local domain.

Additional reference words: 3.51
KBCategory: kbprg kbprb
KBSubcategory: NtwkRpc

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: November 29, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.