Re: Different scan ranges yield different results

[Brandon Enright <bmenrigh () ucsd edu>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Sergio,

I don't think anyone has any ideas jumping out at them.  I thin the
only way you'll be able to troubleshoot this is via -d3 --packet-trace

If you can try to cut down the scan sizes and options as much as
possible while still reproducing the bug go ahead and send the traces
to the list and someone will probably look at them

Brandon


On Fri, 16 May 2008 12:44:11 -0500
"Sergio Castro" <sergio.castro () unicin net> wrote:

> Hi,
>  
> I ran this scan in my LAN:
>  
> nmap 192.168.75.100-160 -vv
>  
> and got results for x.126, x.127, x.129 , and x.150
>  
>  
> But when I ran:
>  
> nmap 192.168.75.150-160 -vv 
>  
> I got resutls for x.153, x.154, and x.155
>  
> Why wouldn't the first scan, which contains the range of the second
> scan, find these last IPs 150 to 155?
>  
> I've seen this result in public IPs also. Any ideas?
>  
> regards,
>  
> Sergio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkgt3YsACgkQqaGPzAsl94IdVQCeIuRDoqUjOEQk5jsdiEK+yLlC
obIAmwYr8V2T1wu0rog7mYbAxn34f3eH
=GyGO
-----END PGP SIGNATURE-----

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