On Wed, 28 Jan 2009, Gene Heskett wrote:

[root@coyote media]# /usr/bin/smbclient '//not.a.host.name/notashare' -U
nosuchuser -N -Tx /dev/null
timeout connecting to 208.69.32.132:445
timeout connecting to 208.69.32.132:139
Error connecting to 208.69.32.132 (Operation already in progress)
Connection to not.a.host.name failed (Error NT_STATUS_ACCESS_DENIED)

That IP address resolves to hit-nxdomain.opendns.com, but the ports
it fails to connect to are microsoft-ds and netbios-ssn. So the DNS
query is not (altogether) failing, and smbclient is trying to make
connections, which eventually time out since there isn't really any
smb service at that address.

It seems the opendns name servers (208.67.222.222 and 208.67.220.220)
are returning one of their own for IP names they don't recognize, in
addition to reporting "not found":

 $ host foo.bar 208.67.220.220
 Using domain server:
 Name: 208.67.220.220
 Address: 208.67.220.220#53
 Aliases:

 foo.bar has address 208.69.36.132
 Host foo.bar not found: 3(NXDOMAIN)

Is this expected behavior? I've never seen it before. In this
scenario, even a guaranteed-bogus IP name won't help.

Nick

****************************************************************
 Nick Russo   email: nick AT cs.uchicago DOT edu   phone: 773.702.3438
    Computer Science Department   The University of Chicago
     Associate Director of Computing Systems, Systems Lead