nmblook up and 95 craziness.

[gandalf at pobox.com]

I've been trying to figure out why many versions of 95 do not respond to
nmblookup (or any name queries for that matter).  I discovered something
that I would assume is known by now, but I have not seen mentioned in the
list archives.  

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?

Here are some relevent dumps:

(two invalid responces from 95 via tcpdump)
13:43:59.841721 ip-216-46-81-66.terabit.net.netbios-ns >
otherland.darkcorner.net.netbios-ns: udp 211
13:44:04.872897 ip-216-46-81-66.terabit.net.netbios-ns >
otherland.darkcorner.net.netbios-ns: udp 211
                        

(two log entries from nmbd, since it is listening to 137)
1999/09/02 13:43:59, 0]
nmbd/nmbd_responserecordsdb.c:find_response_record(240)
find_response_record: response packet id 10028 received with no matching
record.
[1999/09/02 13:43:59, 0]
nmbd/nmbd_packets.c:find_subnet_for_nmb_packet(1412)
find_subnet_for_nmb_packet: response record not found for response id
10028

[1999/09/02 13:44:04, 0]
nmbd/nmbd_responserecordsdb.c:find_response_record(240)
find_response_record: response packet id 10028 received with no matching
record.
[1999/09/02 13:44:04, 0]
nmbd/nmbd_packets.c:find_subnet_for_nmb_packet(1412)
find_subnet_for_nmb_packet: response record not found for response id
10028