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

[Christopher R. Hertel]

On Tue, Dec 28, 2004 at 02:33:30PM -0800, David Wuertele wrote:
> >> # 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?

That is weird!

It's the Workstation Service that is supposed to listen for <00> names.  
The Messenger service listens for the MACHINE<03> or USER<03> name (older 
implementations used MACHINE<01>).

Does XP have a "Workstation Service"?

Very strange.

Chris -)-----

--
"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/     -)-----   crh at ubiqx.mn.org
OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh at ubiqx.org