Have Geek Brain

Possible problems switching from "ncalrpc" to "ncacn_np"

I have an application that uses RPC for interprocess communication. It turns out that synchronous RPC pipes used with the "ncalrpc" protocol sequence are not visible in Vista. I want to switch to "ncacn_np" and use RpcServerRegisterEpEx () with the RPC_IF_ALLOW_LOCAL_ONLY flag.

Has anyone else tried it? Are there any potential issues with this transition?

0


a source to share


1 answer


You saw this information about using flags:

... When this interface flag is registered, the RPC runtime rejects calls made by remote clients. All local calls using the ncadg_ * and ncacn_ * protocol sequences are also rejected, except for ncacn_np. RPC only allows ncacn_NP calls if the call is not coming from the SRV. Calls from ncalrpc are always processed ...



RPC for local use LPC (Microsoft Windows Internals 4 ed, fron page 802):
Local RPC can be used to communicate between two processes located on the same system, and the RPC runtime DLL uses local procedure call (LPC) facilities in kernel as a local network API.

[Changed]
Additional help How to troubleshoot connectivity problems caused by RPC protocol registry entries

+2


a source






More articles:


All Articles