nmblook up and 95 craziness.

[Herb Lewis]

gandalf at pobox.com wrote:
> 
> Anyhow, when you send a name request from some random port to 95, 95
> responds to the request, not on the port that you sent the message from,
> but back to port 137 on the src machine.  Why on earth would they do that?
> Is there a way to tell 95 to be sane?  I would really like to be able to
> get the name responce from 95 machines, but this is insane.  Is there
> anything I can do?
> 

This is a known bug with win95. The only workaround I have seen is to
run your query as root so you can bind to port 137 and make sure nmbd
is not running (so it hasn't already bound to the port).

See the description of the -r option in the nmblookup man page.

-- 
======================================================================
Herb Lewis                                   Silicon Graphics 
Technical Marketing                          2011 N Shoreline Blvd
Network Systems Division                     Mountain View, CA  94043  
herb at sgi.com                                 Tel: 650-933-2177
http://www.sgi.com                           Fax: 650-932-2177          
======================================================================