Comment 9 for bug 363576

Thanks for the extra info. I think there is no bug here.
When you use libsmbclient (by smbclient or nautilus) to access "//nasdrive/public" it must first resolve nasdrive to an IP address. It does so by several methods, trying by default in that order: lmhosts, host, wins, bcast. In your case it first tries to find "nasdrive" in /etc/samba/lmhosts but it's not there. Then it tries classic name resolution... and there it finds a match: nasdrive = 206.112.100.151.

So it means something in your name resolution (/etc/hosts file, DNS...) resolves "nasdrive" as "206.112.100.151". For example you're using OpenDNS and it is kind enough to answer something completely wrong based on its search engine. In all cases, it's not a bug in samba.

Solutions to fixing it include:
- rename "nasdrive" to something your name resolution won't find
- fix your name resolution so that "ping nasdrive" doesn't go to 206.112.100.151
- add nasdrive to your lmhosts file
- changing "name resolve order" in /etc/samba/smb.conf so that bcast appears before host and the nasdrive name is found by broadcast rather than host resolution (noisy and wrong, like what Windows does)