Require nmbd for NetBIOS, even for client code?
rpenny at samba.org
Thu Jan 25 17:36:54 UTC 2018
On Thu, 25 Jan 2018 18:19:26 +0100
Andreas Schneider via samba-technical <samba-technical at lists.samba.org>
> On Thursday, 25 January 2018 09:20:07 CET Volker Lendecke via
> samba-technical wrote:
> > Hi!
> > Right now I'm trying to streamline our DC lookup. On that way I am
> > digging through our NetBIOS name lookup routines, which I believe we
> > can't drop yet. To significantly simplify them I would like to make
> > the following change: I would make nmbd accept packets to send out
> > via NetBIOS on the "unexpected" socket. This would mean that our
> > NetBIOS name lookup requests will also come from port 137, which
> > makes us more compatible with the legacy stuff. I would remove the
> > code that sends out packets via individual sockets. For the replies
> > we have to listen on the "unexpected" pipe *and* the sending
> > socket, which is pretty ugly. My patchset would make that a single
> > point of NetBIOS "calls".
> > However, this would mean that nmblookup & friends (and also "net rpc
> > join" to a classic domain") would require nmbd to run for the
> > lookups.
> > By the way, for proper operation winbind in a classic domain already
> > does require nmbd to run to make the getdc dgram requests. They
> > *must* come from 138.
> > Any objections?
> No, I think people normally run it anyway. Sounds fine!
Just a thought, would it be an idea to update smb.conf about this?
I am referring to the 'disable netbios' parameter.
More information about the samba-technical