mailing list archives
Re: nmap v6.00: Strange connect error from 192.168.1.1 (10048): Only one usage of each socket address (protocol/network address/port) is normally permitted. Assertion failed: 0, file src\nsock_core.c, line 364
From: David Fifield <david () bamsoftware com>
Date: Tue, 29 May 2012 13:27:26 -0700
On Tue, May 29, 2012 at 08:11:31PM +0000, Jeff Kayser wrote:
Version of nmap installed: 6.00
Version of WinPcap installed: 4.1.2
Computer onto which I installed nmap v6.00:
Windows 7 Professional SP1 64-bit.
Nmap command run:
nmap -sS -sU -T4 -A -v -PE -PP -PS21,22,23,25,80,113,31339 -PA80,113,443,10042 -PO --script all 192.168.1.1-254
Nmap output with error at the bottom:
Starting Nmap 6.00 ( http://nmap.org ) at 2012-05-28 10:20 Pacific Daylight Time
NSE: Loaded 348 scripts for scanning.
Initiating OS detection (try #1) against 192.168.1.1
NSE: Script scanning 192.168.1.1.
Initiating NSE at 10:39
Discovered open port 67/udp on 192.168.1.1
Discovered open port 1900/udp on 192.168.1.1
Strange connect error from 192.168.1.1 (10048): Only one usage of each socket address (protocol/network address/port)
is normally permitted. Assertion failed: 0, file src\nsock_core.c, line 364
10048 is WSAEADDRINUSE. My guess is that maybe two different scripts are
trying to bind to the same local UDP port?
As an aside, it looks like your scan profiles are from a previous
version of Zenmap. We don't recommend using "--script all" any longer.
If you delete your scan_profile.usp file, it will be restored to the new
defaults. Otherwise this is the new "Slow comprehensive scan":
nmap -sS -sU -T4 -A -v -PE -PS80,443 -PA3389 -PP -PU40125 -PY --source-port 53 --script "default or (discovery
Sent through the nmap-dev mailing list
Archived at http://seclists.org/nmap-dev/