The information in this article applies to:
SUMMARYUnder Windows 95, a client application calls RpcBindingSetAuthInfo to set up a binding handle for an authenticated remote procedure call (RPC). If this is called with a NULL server principal name and the binding handle is not fully bound, RpcBindingSetAuthInfo fails with error 1819, RPC_S_BINDING_INCOMPLETE. In this case, you must use RpcEpResolveBinding to fully resolve the binding handle before calling RpcBindingSetAuthInfo. This article demonstrates how to do this. MORE INFORMATIONUse the following sample code to use RpcEpResolveBinding to fully resolve the binding handle before calling RpcBindingSetAuthInfo: Sample Code
Under Windows 95, if RpcBindingSetAuthInfo is called with a NULL server
principal name, the binding handle must be fully bound. If the server
registers the endpoint with the endpoint mapper in a dynamic endpoint
(which is not known by the client), you must use RpcEpResolveBinding to
bind the handle. You must do this because the Windows 95 run-time library
implicitly calls RpcMgmtInqServerPrincName to obtain the principal name
from the server, and you cannot make calls to management interfaces to
unbound handles. All RPC server processes have the same management
interface. Registering the handle with the endpoint mapper is not
sufficient to uniquely identify a server.
REFERENCES
Platform SDK documentation: RPC; Windows 95
Q142064 RPC Authentication Option Under Windows NT Additional query words: RpcBindingSetAuthInfo
Keywords : kbnetwork kbAPI kbRPC kbSDKPlatform kbWinOS95 kbGrpNet |
Last Reviewed: January 13, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |