winbindd architecture

[Christopher R. Hertel]

On Fri, Jul 12, 2002 at 02:07:29AM +0930, Richard Sharpe wrote:
> On Thu, 11 Jul 2002, Tim Potter wrote:
> 
> > On Thu, Jul 11, 2002 at 03:57:11PM -0400, Leducq Dominique wrote:
> > 
> > > Le Mercredi 20 F?vrier 2002 12:51, Tim Potter a ?crit :
> > > > 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.
> > > 
> > > I would need some more details about this. Could you please tell me :
> > > 
> > > - which versions of the OS are involved (NT 4 to XP) ? Only as PDC ?
> > > - which kind of requests ? 
> > > - which port ? (I guess it replies to port 137 or 445 instead of source port 
> > > of the request...)
> > 
> > >From memory it is the network request that locates the PDC name on the
> > network.  I think it is only Windows NT 4 but I haven't tested it.  It
> > is one of the udp ports - 139 I think.
> 
> Also from memory, but I believe that Win9X does that as well. I think name 
> lookup requests to a Win9X machine are sent back to port 137.

As far as I know, NT replies correctly to name queries and node status 
queries (both on port 137).  The help generated by 'nmblookup -?' state 
that it's only W/95 that has this problem, and I think it's only early 
versions of W/95, and only when sent a Node Status query.

I have a test machine at home which runs W/95, responds correctly to a 
Name Query, but responds to port 137 when sent a Node Status.

Chris -)-----

-- 
Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/     -)-----   crh at ubiqx.mn.org
OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh at ubiqx.org