Re: Security callback failure in XP-SP1

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Gianluca Braccini (gbraccini_at_tiscalinet.it)
Date: 02/23/05 

Date: Wed, 23 Feb 2005 11:05:51 +0100

I don't know if this can help you, but when i use rpc secure with a security
callback that validate the client i return RPC_S_OK and not RPC_OK; i don't
know if it's the same value.

Gianluca

"Gianluca Braccini" <gbraccini@tiscalinet.it> ha scritto nel messaggio
news:%23ObjL6YGFHA.1084@tk2msftngp13.phx.gbl...
> Yes it's the same for my code. I set NULL the SecurityCallback parameter.
>
> Gianluca
>
> "Mickey" <Mickey@discussions.microsoft.com> ha scritto nel messaggio
> news:CB454338-F6EE-4BAD-B268-7ADE2E8DEB98@microsoft.com...
> > I dont us authentication.
> > Server and Client run XP-SP1 tcp_ip.
> > In order to provide a workaround for XP-SP2 security I provide as
advised:
> > RpcServerRegisterIfEx(ServerIfHandle, NULL,NULL,
> >
>
RPC_IF_ALLOW_CALLBACKS_WITH_NO_AUTH,RPC_C_LISTEN_MAX_CALLS_DEFAULT,SecurityC
> allback);
> >
> > SecurityCallback is an empty function that alwasys returns RPC_OK;
> >
> > On RPC call the client fails with Access denied (0x0000005) exception.
> >
> > When running on XP-SP2 everything works fine.
> > When assigning NULL instead of function name, it works fine.
> > Have anybody seen something like this?
> > Thanks in advance.
>
>

Relevant Pages