Since you mention Superscan, I am going to assume that you are doing this on a
windows system. Most likely a windows XP SP2 system. SP2 drastically changed
the way the TCP/IP stack works in XP and thus created numerous problems with
port scanning tools. I can't speak for the other tools you mention, having
never run them from a windows XP box, but I know for a fact that Superscan
results are unpredictable after installing SP2. You may want to try making your
scan smaller, and running 'net stop shared services' before launching your
scan. Sometimes, running Superscan twice will yield accurate results the second
time. One last thing you may want to try is to use a full connect scan with
superscan. This is very noisy, but the syn scan is flaky at best with SP2.
I've reached the point where I no longer use superscan for these reasons, which
is unfortunate, because it used to work really well.
I'm sure others on the list can speak about running the other tools and getting
better results from them.
------------------------------------------------------------------------
This List Sponsored by: Cenzic
Are you using SPI, Watchfire or WhiteHat?
Consider getting clear vision with Cenzic
See HOW Now with our 20/20 program!
http://www.cenzic.com/c/2020
------------------------------------------------------------------------
|