David Fifield wrote:
> On Sun, Dec 09, 2007 at 03:16:35AM +0000, jah wrote:
>
>> As to the Unknown Error:
>> This seems to refer to errbuf in PacketTrace::traceConnect in tcpip.cc:771
>> Does anyone have any idea what could be wrong?
>> The error occurs in 4.20 too, so it's not a recently introduced bug.
>> Whatever it is prevents further packet tracing.
>>
>
> That's because Windows returns an unhandled error code, WSAEWOULDBLOCK,
> which is not really an error but means "operation in progress." See
> http://seclists.org/nmap-dev/2007/q3/0417.html. It probably ought to be
> changed some time.
>
>
>
Aye, it's not a showstopper, but it reduces the usefulness of packet
tracing with connect scans on windows.
And it definitely does occur in 4.20 which is interesting given Robs
observation (http://seclists.org/nmap-dev/2007/q3/0410.html)
"Running the exact same command with nmap 4.11, 4.21-A1, 4.22SOC2,
4.22SOC3, 4.22SOC5 appears to work fine. This seems to have started with
4.22SOC6."
jah
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
Received on Dec 08 2007
Intro
