Re: nmap 6 issue

[David Fifield <david () bamsoftware com>]

On Sun, May 27, 2012 at 10:59:59PM -0700, David Fifield wrote:
> On Fri, May 25, 2012 at 07:34:09PM +0000, Jerry Riedel wrote:
> > 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.
>
> The VPN might be the problem. Can you send me the --iflist output?

Does this also happen when you scan the targets
        192.168.0.1-254
and what about
        192.168.0.0
and
        192.168.0.255
individually?

The immediate cause of this error message is r24413, which changed the
way source addresses are computed.

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