Nmap loops with "Unable to find listening socket in get_rpc_results" error

[Lionel Cons <lionel.cons () cern ch>]

Hello,

I've recently detected a weird problem with some of my Nmap scans. In
some cases, Nmap goes crazy in the RPC scan and outputs the following
line repeatedly on stderr:

  Unable to find listening socket in get_rpc_results

I've recompiled Nmap from SVN (revision 15724) and still get the same
behaviour.

Here is how the scan output could look like:

Starting Nmap 5.05BETA1 ( http://nmap.org ) at 2009-10-06 15:07 CEST
Stats: 0:03:10 elapsed; 0 hosts completed (1 up), 1 undergoing Service Scan
Service scan Timing: About 96.77% done; ETC: 15:10 (0:00:06 remaining)
Stats: 0:04:23 elapsed; 0 hosts completed (1 up), 1 undergoing RPCGrind Scan
Stats: 0:05:22 elapsed; 0 hosts completed (1 up), 1 undergoing RPCGrind Scan
Stats: 0:07:00 elapsed; 0 hosts completed (1 up), 1 undergoing RPCGrind Scan
Unable to find listening socket in get_rpc_results
Unable to find listening socket in get_rpc_results
Unable to find listening socket in get_rpc_results
Unable to find listening socket in get_rpc_results
Unable to find listening socket in get_rpc_results
Unable to find listening socket in get_rpc_results
Unable to find listening socket in get_rpc_results
Unable to find listening socket in get_rpc_results
Unable to find listening socket in get_rpc_results
Unable to find listening socket in get_rpc_results
[...]

FWIW, I started Nmap with:

# nmap -O -sS -sU -sR -sV --version-intensity 8 --host-timeout 2h -p 
T:1-65535,U:53,69,111,123,137-139,161,177,445,623,1434,1900,7000-7009 <victim-ip>

The exact same arguments work well for other targets...

Any idea what could be wrong?

Cheers,

Lionel

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org