Bug 8927 - nmblookup prints just one record and exits
Summary: nmblookup prints just one record and exits
Alias: None
Product: Samba 3.6
Classification: Unclassified
Component: Client Tools (show other bugs)
Version: 3.6.4
Hardware: All All
: P5 normal
Target Milestone: ---
Assignee: Jeremy Allison
QA Contact: Samba QA Contact
Depends on:
Reported: 2012-05-10 16:29 UTC by Giulio
Modified: 2021-11-21 19:55 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Giulio 2012-05-10 16:29:16 UTC
I'm using samba binaries from sernet (OS is Linux RHEL5).

nmblookup from samba-3.6 will print just the first record and exits.

  $ nmblookup '*'
  querying * on *<00>

samba-3.5.13 (samba-3.0.x is the same):
  $ nmblookup '*'
  querying * on *<00> *<00> *<00> *<00> *<00> *<00> *<00> *<00> *<00>

- the above output is from 2 samba's on the same subnet running at the same time; I can assure you there are no network issues, the IP of the samba-3.6 system is shown in the output of the samba-3.5's nmblookup.

- If i run "nmblookup __SAMBA__":
  * samba < 3.6: will display all the samba systems on the network
  * samba 3.6: will display randomly just 1 samba system
Comment 1 Mayk 2014-08-06 09:44:43 UTC
No update for more than two years ... this bug is still present in nmblookup for samba 4. It's the reason why findsmb no longer works, and why findsmb might be dropped from debian/jessie altogether.

Is there a new/better way to invoke nmblookup these days to do exactly what nmblokup '*' was capable of?

* find all samba ips
* in all domains
* querying broadcast and not the master browser

If there is a new way, please tell me so. I'll send a patch to debian and fix findsmb, preferably in time for the feature freeze.


Comment 2 Jeremy Allison 2014-08-07 15:53:09 UTC
Just not been considered a high priority, sorry. I'll try and take a look to see if there's an easy way to do what you ask.
Comment 3 Mayk 2014-08-14 16:23:17 UTC
Jeremy, thanks for taking your time and look at it. There's just nothing as easy out there, that will let you collect all netbios ips like nmblookup '*' was able to do. It also was step one for debugging network issues (Check your ips, resolve them to shares, identify current master browser, identify machines that have gone offline). So I doubt this feature is pure low priority.