dce/rpc "client" api

Sander Striker s.striker at striker.nl
Mon Aug 21 16:29:48 GMT 2000

>I was under the impression that each transport 
>layer would have its own endport mapper.  For example,
>a dce/rpc over SMB would listen on port 139 (or 445 
>depending).  A dce/rpc over TCP would listen on 
>another published port.

Ah, ok. What about the nameservice then? RPC servers
are 'supposed to' register themselves so clients can
easiliy find them, on whatever transport. Without this
kind of support you can only use well known endpoints 
_in combination with_ well a known transport layer.


PS. I think it's time that someone paints the big picture...

More information about the samba-technical mailing list