slower when running on windows
Closed this issue · 0 comments
Threader3000 is a great tool.
I am amazed at just how fast threader3000 runs its initial scan. I've installed threader3000 on all kinds of Linux hosts with great results in all cases.
Now I have installed threader3000 on a Windows 10 machine, and I notice that the initial nmap scan, which I would expect to take a few seconds, takes 1 minute 41 seconds. I see no output until the scan completes.
Exactly the same symptom for Git Bash and Cygwin terminal windows.
When run from a normal cmd.exe prompt, I get the same result, except that I immediately see the comforting "Port nnn is open..." throughout the duration of the scan.
I have tested nmap.exe (V.7.70) by itself and found that scanning all 65,535 TCP ports on localhost takes 1.76 seconds using the T5 flag. Threader3000's initial nmap scan reliably takes 1 minute 41 seconds to complete on localhost.
This is certainly not a deal-breaker, but I am curious as to why this is happening, and what I might be able to troubleshoot and/or analyze.