Different scan ranges yield different results

5 msg	Large update/recode of NSE (test please)
2 msg	Nmap/Zenmap 4.62-test8 packages for Mac OS X
1 msg	Silent Installation?
4 msg	nmap error
2 msg	[PATCH] Fix IPv6 scanning against link-local ad...
2 msg	PATCH: nsock_core.c / do_actual_read() / recv v...
3 msg	Unofficial WinPcap Installer Issue
5 msg	The difficulty of running Nmap with privileges ...
1 msg	Script scan error
1 msg	Mac OS X VPN Client

Different scan ranges yield different results
\ Sergio Castro (16 May 2008)
. \ Brandon Enright (16 May 2008)
. . \ Sergio Castro (16 May 2008)

1 msg	RFE: Pseudo target for local network(s)
1 msg	seclists.org RSS feeds, now with message excerpts
1 msg	nmap_command_path patch
1 msg	NSE Idea: Script to show SSHD host fingerprints
19 msg	nmap issue
2 msg	nsock_connect_ssl: bad version identification?
1 msg	Minor bug in nmap_dns.cc
2 msg	configure fails to detect g++
2 msg	hostname bug by scannig a server.

Subject:	Different scan ranges yield different results
Group:	Nmap-dev
From:	Sergio Castro
Date:	16 May 2008

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

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