Bug 498 - WINS server reports wrong address (ignores interfaces/bind interfaces)
Summary: WINS server reports wrong address (ignores interfaces/bind interfaces)
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: nmbd (show other bugs)
Version: 3.0.11
Hardware: All Linux
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact:
Depends on:
Reported: 2003-09-23 12:24 UTC by Joe Frisbie
Modified: 2009-07-02 05:17 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Joe Frisbie 2003-09-23 12:24:14 UTC
On a linux machine with the following interfaces configured:

dev     address       netmask        broadcast






And with an smb.conf of:



  workgroup = SENS

  server string = File Server

  netbios name = files-0

  ## Security

#  hosts allow = 10.36.70.

  encrypt passwords = yes

  security = user

  ## Nework

  socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

  interfaces =

  bind interfaces only = yes

  ## WinDNS

  wins support = yes

  name resolve order = wins


  path = /tmp

  read only = no

  guest ok = yes

One would expect that would be reported for address

of files-0. In fact, "nmblookup -R -U files-0" yeilds:

added interface ip= bcast= nmask=

added interface ip= bcast= nmask=

querying files-0 on

Got a positive name query response from ( ) files-0<00> files-0<00> files-0<00> files-0<00> files-0<00>

Although, is listed first, it (almost?) never gets chosen. When

one of the other addresses is used, no connection can be made because 

smbd (?) is listening only on This makes it effectively 

impossible to use the Samba WINS server functionality restricted to only

one network address.
Comment 1 Joe Frisbie 2003-09-24 05:24:49 UTC
Umm, deleting /var/cache/samba/wins.dat fixed the problem. I guess

this a cache that was stale. Perhaps a mention in the documentation

would help.
Comment 2 SATOH Fumiyasu 2004-02-24 01:51:39 UTC
Add Cc to track this bug.
Comment 3 SATOH Fumiyasu 2004-02-24 02:00:58 UTC
I can reproduce a similar problem. If the interfaces parameter has loopback
interface (interface name (e.g. "lo" on Linux), or
and another interface, nmbd registers a strange IP address.

interfaces =

test command-line
$ nmblookup -U '*'
querying * on *<00> *<00>

Comment 4 Gerald (Jerry) Carter (dead mail address) 2005-02-07 09:12:19 UTC
originally against 3.0.0rc4
Comment 5 jdppm7 2006-11-15 14:55:26 UTC
Here's why deleting the wins.dat file works in some instances:

The original smb.conf did NOT have the correct interfaces/bind interfaces only directives. SAMBA created the wins.dat file, including the entries for this server, its workgroup, etc. The directives were added but, upon restart, SAMBA did not do any sanity checks to make sure that its own entries in wins.dat were indeed correct.
Comment 6 SATOH Fumiyasu 2007-02-21 10:35:20 UTC
This bug can be reproducable with Samba 3.0.24 on Debian unstable (Linux kernel, but not on Solaris 10.
Comment 7 SATOH Fumiyasu 2007-11-19 19:27:21 UTC
I think this bug was fixed by:


I've confirmed with Samba 3.0.24 + the above changes.
Comment 8 Matthias Dieter Wallnöfer 2009-07-02 05:17:19 UTC
If it seems that it has been fixed then mark it as "FIXED".