Gordon Ross wrote: > Have a look at a snoop capture (use wireshark to view it). > If you see no NetBIOS responses, You'll probably find that > NetBIOS is not running on the box you're trying to reach.
I don't know what the difference is between all these things. If I can discover filesystems on the other machine using Windows Explorer, and I can access files on the other machine, doesn't that imply that NetBIOS is running on the other machine? If not, what do I do in Windows to cause NetBIOS to be running? >> FYI, it works when finding my *own* address: >> >> nissan$ smbutil lookup nissan >> Got response from 192.168.0.2 >> IP address of nissan: 192.168.0.2 >> >> But I assumed the point of it was to find the address of *other* >> machines. >> [...] > > Yes, that is the point, but the local "nmbd" is not involved. > If you have a WINS running and configured (see wins in the > nsmbrc(4) man page) then that could help. Based on a (too quick) read of that man page, I created a .nsmbrc file containing: [default] domain=WORKGROUP user=guest It made no difference. I'll go back and read it more thoroughly to see if there's something I missed, but it sure doesn't seem like it should be this hard. _______________________________________________ cifs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
