On April 2, 2003 09:02 am, Gregory M. Turner wrote:
On Monday 31 March 2003 11:40 am, Bill Medland wrote:
The builtin rpcrt4 fails on a call to unimplemented RpcServerInqDefaultPrincName but I don't understand why it is even calling that; why does it think I have Netware only and why does it think this is a server process.
What does that have to do with netware? As far as I know, the security principal is the backbone of the NT domain's and DCOM's security model.
Probably just crappy docs. IIRC DCE RPC does define an equivalent API, so it ought to have some non-netware applications as well. Probably, stubs for more of the RPC security and name services API's would be helpful here, if only to expose a new landscape of unimplemented functionality ;)
So to recreate this, what does one do exactly? DCOMTST does it with native rpcrt4? Or some other setup?
(Ref. MSDN Q259011) The DCOMTEST program pair is based on the simple DCOM sample provided with the platform SDK.
In what way it is different I don't know but it is basically the same.
As far as we are concerned the first stumbling block is a call to CoCreateInstanceEx with a non-null server.
To get anywhere you will need to use the native ole32.