wxp SP2 host responds to "nmblookup HOST" but not "nmblookup *"

[David Wuertele]

>> # nmblookup '*' -U
>> creating lame upcase table
>> creating lame lowcase table
>> querying * on 192.168.0.255
>> 192.168.0.15 *<00>
>> # 
>> 
>> Alas, the results are the same.

CH> I was afraid of that.  Seems they've simply broken it.


More data:  turning on the "Messenger" service on 192.168.0.7 made it
respond to wildcard broadcast queries!?! WTF???

  # nmblookup '*'
  creating lame upcase table
  creating lame lowcase table
  querying * on 192.168.0.255
  192.168.0.15 *<00>
  192.168.0.7 *<00>

I didn't realize the messenger service was handling this.  Or is it
that some security logic is only turning on the "respond to wildcard"
feature if it sees that the messenger service is running?

Dave