Re: Nmap loops with "Unable to find listening socket in get_rpc_results" error [2]

[Fyodor <fyodor () insecure org>]

On Mon, Oct 19, 2009 at 04:37:39PM +0200, Lionel Cons wrote:
> Hello,
>
> I still suffer from the problem described two weeks ago on this list
> (see http://seclists.org/nmap-dev/2009/q4/24).

Hi Lionel.  Thanks for the report.  I have a few questions:

o Does this happen pretty much every time you scan the target machine,
  or is it intermittent.

o The command you noted is:

  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>

Can you try to reduce that step by step until you can find the minimal
command which still reproduces the problem?  Reduction steps include:
 o Remove -sU
 o Do a plain port scan and see what ports are open.  Try with just
   those ports, then reduce one by one and maybe you can find just one
   port which is causing this.
 o Remove extra parameters like -O and --version-intensity and -sR one
   until you find the smallest set needed to reproduce the problem.
 o Once you have your minimum command, please try with -d5 and send me
  the output.
 o Only one system does this to you?  Is it on the Internet where I
   can scan it, or an internal system?  What do you get from "rpcinfo -p
   <target>" and "nmap -p- -A -T4 <target>"?

Thanks,
Fyodor
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/