dce/rpc services (Was: dce/rpc client api)

[Todd Sabin]

Luke Kenneth Casson Leighton <lkcl at samba.org> writes:

> ncacn_np endpoint format contains sufficient info for there to be no
> _need_ to have an endport mapper.  this is _not_ the case for any other
> transport, as far as i am aware.  all other transports contain the

I'm pretty sure that all string bindings contain sufficient info to
make a connection without the assistance of the epmapper.  The
epmapper comes into play when you know you want interface
12345678-90ab-1234-etc. on a given machine, but you don't know where
on that machine to find it.  You then contact the epmapper (which
listens on well-known endpoints for every protseq it supports) and ask
it where you can find 12345678....

> abstract syntax identifier and also some sort of port number (or
> equivalent):
> 
> remember format of ncacn_np:
> 
> ncacn_np://server/pipe/pipe_name
> 
> remember format of ncacn_tcp:
> 
> ncacn_tcp://server/123456789abcdef-1234-5678:[8080]

Where did you get these formats from?  They're not what NT uses,
though maybe the format of string bindings isn't standardized across
dce/rpc implementations.  FYI, NT would use
ncacn_np:\\server[\pipe\pipe_name] and ncacn_ip_tcp:ip[port].

If you haven't seen it, check out the opengroup's specification for
dce/rpc 1.1, at http://www.opengroup.org/onlinepubs/9629399/toc.htm.
I've been looking it over recently, and it's pretty good.


Todd