DCE/RPC over TCP

[Seiichi Tatsukawa]

The first TCP/IP connection is to the DCE endpoint mapper (port 135).

ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers
  epmap           135/tcp    DCE endpoint resolution
  epmap           135/udp    DCE endpoint resolution
  #                          Joe Pato <pato at apollo.hp.com>

It's doing ept_map() RPC which returns the RPC protocol towers. Its
interface definition is in
http://www.opengroup.org/onlinepubs/9629399/apdxo.htm and the protocol
tower encoding is in http://www.opengroup.org/onlinepubs/9629399/apdxl.htm
. (DCE/RPC Specification,
http://www.opengroup.org/onlinepubs/9629399/toc.htm , explains how the
endpoint mapper works. Also, getting familiar with the client context
handle used by ept_map() may help implementing LSA RPCs.)

Samba will need to implement its own endpoint mapper (for systems without
DCE) and/or work with the already existing endpoint mapper. Some
commercial Unixes come with the DCE endpoint mapper (rpcd or dced,
listening on both TCP and UDP ports) which may not be replaceable with
Samba's endpoint mapper (unless it's the full implementation :-). Even
Linux may be running dced (http://www.bu.edu/~jrd/FreeDCE/). On systems
with DCE, you can register Samba's whatever RPC server endpoints by using
the rpccp or dcecp command.

The second connection seems to be for the WINS server which endpoint was
obtained from ept_map(). Doesn't this method work only when all domain
master browsers (PDC) are registered with the same WINS server (including
replicas)?

---  Seiichi

                +        Seiichi Tatsukawa         +
                + Rational Software, Lexington, MA +