winbindd architecture

[Tim Potter]

On Thu, Feb 21, 2002 at 09:24:58AM +1030, Richard Sharpe wrote:

> >Nmbd needs to be running on the local system as there are some lookup
> >requests send by winbindd that are sent by Windows NT domain controllers
> >to the incorrect port which is a bug in Windows.  Nmbd receives these
> >packets and stores them in a database (unexpected.tdb) which winbindd
> >reads from.
> 
> Hmmm, this does not cause us a problem, but then, now that I think about 
> it, we run nmbd on the local system.

I think there are a handful of calls that respond to the wrong port.
A domain controller lookup function is one of them but I can't remember
the name of it.  (-:

Signs that you should be running nmbd with winbindd are when winbindd
won't start up because it can't locate the domain controller for a
domain even though it is reachable.


Tim.