Nmap Development mailing list archives

nsock_loop error


From: "Dr. John S Pemberton" <drccjsp () hotmail com>
Date: Tue, 15 Jun 2004 09:49:06 +0200

References:
http://seclists.org/lists/nmap-dev/2003/Oct-Dec/0058.html
http://seclists.org/lists/nmap-dev/2004/Apr-Jun/0032.html

I still get the nsock_loop error when running the Win32 build. From what I
can tell, the following triggers the error:

* you do version scanning
* you get exactly one open UDP port

i.e.
nmap -sUV -p 50-55 host.example.com [and that host has only one of those
open]

Running W2K or XP doesn't matter. Under the same conditions but scanning TCP
only, using -sSV, no error occurs. The number of ports scanned for doesn't
seem to matter, just that you get one open port as a result. Scanning TCP
and UDP at the same time doesn't matter, the error is still trigged when
there is *one* open UDP port. And no, it does not have to be port 53.

Anyone feeling you've got the skills, please look into this!

/jp

---------------------------------------------------------------------
For help using this (nmap-dev) mailing list, send a blank email to 
nmap-dev-help () insecure org . List archive: http://seclists.org



Current thread: