Nmap Development mailing list archives
nsock_loop error still there in 3.55/win32
From: "Dr. John S Pemberton" <drccjsp () hotmail com>
Date: Thu, 15 Jul 2004 09:05:18 +0200
References: http://seclists.org/lists/nmap-dev/2003/Oct-Dec/0058.html http://seclists.org/lists/nmap-dev/2004/Apr-Jun/0032.html http://seclists.org/lists/nmap-dev/2004/Apr-Jun/0070.html I still get the nsock_loop error when running the Win32 build of nmap 3.55 (I've never seen the problem on UNIX). From what I can tell, the following always trigger the error: * you do version scanning * you get exactly one open UDP port i.e. nmap -sUV -p 50-55 ns.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. I use version 3.0 of winpcap. 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:
- nsock_loop error still there in 3.55/win32 Dr. John S Pemberton (Jul 15)