RE: Bug in nmap 3.91 on windows

["Craig Humphrey" <Craig.Humphrey () chapmantripp com>]

Note: if I don't use the host_timeout setting, it works fine!

I guess this means that the response isn't turning up in time.

I did some playing around with host_timeout, for my network (I'm
guessing everyone's will vary slightly), if I set it to >3240 it will
always complete with no errors, between 3200 and 3239 and it will
sometimes fail, but not always.  Any lower and it always fails,
returning the "Failed to determine dst MAC address for target" error.

I'm guessing that this is some kind of clash between the OS's ARP
timeout and Nmap's...  Something like, if the OS times out, it returns a
"no host found" which nmap handles cleanly, but if nmap times out, it
returns the "Failed to determine..." error.

Hope that helps Fyodor.

> -----Original Message-----
> From: nmap-dev-bounces () insecure org 
> [mailto:nmap-dev-bounces () insecure org] On Behalf Of Craig Humphrey
> Sent: Monday, September 12, 2005 9:55 AM
> To: nmap-dev () insecure org
> Subject: RE: Bug in nmap 3.91 on windows
>
> Ditto on WinXpsp2 all patched up. (Note host invoking nmap is 
> 10.9.9.1, no host on 10.9.9.0, so this might relate to the 
> Windows can't scan itself known issue.)
>
> C:\Program Files\nmap>nmap -sP -v -v -d5 -T5 --host_timeout 
> 201 10.9.9.*
> ***WinIP***  trying to initialize winpcap 2.1
> Winpcap present, dynamic linked to: WinPcap version 3.1 
> (packet.dll version 3, 1
> , 0, 27), based on libpcap version 0.9[.x]


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