mathog@seqaxp.bio.caltech.edu
1999-Feb-19 22:51 UTC
findsmb on Linux different than on SGI?
We're running an older version of Samba on an Irix machine, and just got 2.0.2 working (finally!) on our Intel/Linux box. The odd thing, is that findsmb gives different results on the two systms. On Irix it lists the NetBIOS names with OS descriptions, but on Linux it lists the IP name and no OS description. I went through it line by line and found the first difference at: ../nmblookup -r -A $ip when I run that interactively on the Irix system and aim at it any system, for instance, WNT 4 SP3, it comes right back. Do it again without the "-r" it gives the same answer. On Linux, however, it comes back with nothing for the "-r" case, but works fine if I leave that out. So I modified findsmb on Linux to leave off the "-r". I've scanned numerous subnets, and the results now seem to be the same on the SGI and Linux versions. One exception, the Linux variant now sees one [Windows NT 4.0 ] [NT LAN Manager 4.0] box that the SGI doesn't see. I have no idea why (and expected the opposite result) Conclusion: "-r" is broken on the (RedHat) Linux version of nmblookup OR it is broken on some versions later than 1.9.19. Can anybody shed more light on this? Also, is there something faster than findsmb available - it is horrifically slow. Thanks, David Mathog mathog@seqaxp.bio.caltech.edu Manager, sequence analysis facility, biology division, Caltech
> >> Conclusion: "-r" is broken on the (RedHat) Linux version of nmblookup > >> OR it is broken on some versions later than 1.9.19. > > > > Did you kill nmbd first? It is sitting on that port... > > > > You've lost me. Two systems, one Irix, one Linux, running different > versions of Samba. On the former, findsmb works, on the latter it doesn't. > nmbd is running in both cases. Why would I need to kill it?I would say that it CAN'T work on Irix. :-))) But the networking is probably slightly different under Irix. The problem is: "-r" causes the replies to be sent to the port 137 on the Linux box. On the port 137 sits nmbd and listens for packets. So then there are fighting two programs for incoming packets. I don't know what Linux does in this case but apparently the packets are handed to nmbd which doesn't know what to do with it and drops it. Probably under Irix the packets are always handed to the last program which is listening on that port or something like it (or hands it to ALL?!?) - simply it somehow works there... Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name udp 0 0 *:netbios-ns *:* 1649/nmblookup udp 0 0 short.short:netbios-dgm *:* 1374/nmbd udp 0 0 short.short.:netbios-ns *:* 1374/nmbd udp 0 0 *:netbios-dgm *:* 1374/nmbd udp 0 0 *:netbios-ns *:* 1374/nmbd root:/home/root>nmblookup -U win98 win98 10.6.66.2 win98<00> root:/home/root>nmblookup -r win98 -U win98 name_query failed to find name win98 root:/home/root>killall nmbd root:/home/root>nmblookup -r -U win98 win98 10.6.66.2 win98<00>> Thanks, > > David MathogHope this helps, Lace