connection.tdb IP vs. NetBIOS name

Chris Lalancette clalancette at
Sun Dec 7 22:07:49 GMT 2003

	Thanks for responding.  Actually, let's take a step back; looking 
further into it, it looks like this is a problem with Win2k/WinXP clients.  
For example, if I just start up smbd (again, 3.0.0, no nmbd, with the 
smb.conf below), I can connect to it from a Linux client, a WinXP, and a 
Win2k client by the IP address (i.e. \\\temp).  With the Linux 
client, once I have connected, I can run "./smbcontrol smbd ping", and I 
get two replies; one from the main Samba process, and one from the Samba 
process that was forked to take care of the client.  However, if I connect 
from a Win2k/WinXP client, and then run the same smbcontrol statement, I 
only get one reply (from the main Samba process).
	If you need any more information, or you have problems reproducing 
the problem, please let me know and I can provide you more information.
	Again, the server is samba 3.0.0 running on RedHat Linux 9.

Thanks for the help,


        encrypt passwords = Yes
        null passwords = Yes
        netbios name = samba
        workgroup = WORKGROUP
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        security = USER
        map to guest = Bad User
        kernel oplocks = no
        load printers = yes
        printing = cups
        printcap name = cups
        oplocks = no
        oplock contention limit = 0
        path = /tmp
        read only = No
        browseable = Yes
        guest ok = Yes

On Fri, 5 Dec 2003, Gerald (Jerry) Carter wrote:

> Hash: SHA1
> Chris Lalancette wrote:
> > Hello all,
> >         I am having a problem with Samba 3.0.0 (I have actually tested
> > this with 3.0.1pre3, and seem to have the same problem).  I am trying to
> > add a new message to smbcontrol.  I have put the code into smbcontrol.c,
> > and I can deliver messages to the samba processes (using the command
> > line: ./smbcontrol smbd <mymsg>).  The problem is that
> > messages get delivered to the Samba processes differently depending on
> > whether I am connecting to them by IP address, or by NetBIOS name.  If I
> > use the NetBIOS name, the message gets delivered to all processes; if I
> > use the IP address, the message really only gets delivered to the main
> > smbd process (the reason that this is important is that I would like to
> > not use nmbd, if possible).  I have tracked this down in the code, and it
> > seems that the difference is in the way new connections get added to the
> > connection.tdb database.  My question is whether this is intentional, a
> > bug in the client, or a bug in Samba?  
> Chris,  Can you send me a patchfile of your changes?  I need to 
> understand exactly what you are trying to accomplish.
> cheers, jerry
> Version: GnuPG v1.2.1 (GNU/Linux)
> Comment: Using GnuPG with Mozilla -
> XgRKNf9kC83qel+uyKxZaro=
> =eAub

More information about the samba-technical mailing list