Nmap Development mailing list archives
nmap 6 issue
From: Jerry Riedel <riedel () codylabs com>
Date: Fri, 25 May 2012 19:34:09 +0000
Windows XP Pro SP3 in a Windows domain environment. Zenmap/Nmap 5.0 w/Winpcap 4.1.2 works fine. Uninstalled 5.0 and ran 6.0 binary installer. Tried using the existing winpcap 4.1.2 and then uninstalled and tried with the bundled winpcap 4.1.2 and got the same error: Starting Nmap 6.00 ( http://nmap.org ) at 2012-05-25 13:11 Mountain Daylight Time NSE: Loaded 93 scripts for scanning. NSE: Script Pre-scanning. get_srcaddr: can't connect socket: The requested address is not valid in its context. nexthost: failed to determine route to 192.168.0.0 QUITTING! Command line in Zenmap is: nmap -T4 -A -v -PE -PS22,25,80 -PA21,23,80,3389 192.168.0.0/24 Tried nmap -iflist and my LAN adapter is eth0, so tried this: nmap -T4 -A -v -PE -PS22,25,80 -PA21,23,80,3389 -e eth0 192.168.0.0/24 ... and got the same results. Uninstalled 6.0, reinstalled 5.0 and it works fine. Google doesn't show much about this error except in the context of development of older versions. If it matters, I have the ShrewSoft VPN client installed on this computer. Any ideas? Jerry Riedel IT Manager Cody Laboratories Inc. 307-587-7099 ext 163 This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION that may be pursuant to a Confidentiality Agreement or Non-Disclosure Agreement and is intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering this to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us by telephone at (307) 587-7099 or notify us by E-mail at stone () codylabs com<mailto:stone () codylabs com>. Also, please mail a hardcopy of the E-mail to Cody Laboratories, Inc. 601 Yellowstone Ave., Cody, WY 82414 via the U.S. Postal Service. We will reimburse you for all expenses incurred. _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- nmap 6 issue Jerry Riedel (May 26)
- Re: nmap 6 issue David Fifield (May 27)
- Re: nmap 6 issue David Fifield (May 29)
- Re: nmap 6 issue David Fifield (May 27)