outsourcing DCE/RPC to alternate programs - runtime config option

tridge at samba.org tridge at samba.org
Mon Dec 13 18:12:24 GMT 2004


Luke,

 >  yes: the hint is from the response of the rpc bind ack packet: the name
 >  of the server that is actually handling the pipe is put in the
 >  response.

no, thats an endpoint name. On ncacn_np its something like
\pipe\spoolss or \pipe\lsass. On ncacn_ip_tcp its the TCP port
number. 

 >   also, i believe that if you analyse NT 3.5 i expect you'll find that
 >   there, the three services _are_ separate (or at least two of them).

In nt4 they are all in one process. In nt3.1 I can't tell, as it
doesn't support the MGMT interface, so I can't look at the interface
statistics. I'd be genuinely surprised if nt3.5 used 3 separate
daemons, but as I don't have it installed at the moment I can't tell. 

 >  it's such a far cry from the "samba is just a file and
 >  print sharer" argument which jeremy used in 1999 to stop me
 >  advocating improvements to samba 3's smb vfs layer.

You never worked on Samba3. You forked off the samba-tng project in
late 2000, when the released version of Samba was 2.0.7. Version 2.2.0
was done 6 months later. An awful lot has happened since then.

Cheers, Tridge


More information about the samba-technical mailing list