Re: Nmap-4.10

["Jamie Gavahan" <redpike () gmail com>]

On 6/14/06, AgentSmith15 <agentsmith15 () gmail com> wrote:
> Are you using Road Runner?
>
> On 6/14/06, Jamie Gavahan <redpike () gmail com> wrote:
> > Hello all,
> >
> > I've been experiencing problems with Nmap since at least 4.03.  My
> > build environment is Windows XP Pro SP2, Visual C++ 2005 Express,
> > Server 2003 R2 Platform SDK. This problem also occurs with precompiled
> > binaries.
> >
> > When doing small scans like: nmap -v -P0 -p21,22,25,53,80,110,443
> > scanme.insecure.org
> > everything works perfectly and exits normally.
> >
> > This command prints every port trying to be discovered until I quit
> > nmap; ask if you want me to run different commands for diagnosis:
> > nmap-4.10\mswin32\Release>nmap -v -P0 -A -oN nmap.0.log
> > scanme.insecure.org
> >
> > Starting Nmap 4.10 ( http://www.insecure.org/nmap ) at 2006-06-14 18:40
> > Central
> > Daylight Time
> > DNS resolution of 1 IPs took 0.20s.
> > Initiating SYN Stealth Scan against scanme.nmap.org (205.217.153.62) [1679
> > ports
> > ] at 18:40
> > Discovered open port 22/tcp on 205.217.153.62
> > Discovered open port 80/tcp on 205.217.153.62
> > Discovered open port 53/tcp on 205.217.153.62
> > SYN Stealth Scan Timing: About 22.87% done; ETC: 18:42 (0:01:41 remaining)
> > Discovered open port 953/tcp on 205.217.153.62
> > Discovered open port 508/tcp on 205.217.153.62
> > Discovered open port 31/tcp on 205.217.153.62
> > Discovered open port 550/tcp on 205.217.153.62
> > Discovered open port 3006/tcp on 205.217.153.62
> > Discovered open port 489/tcp on 205.217.153.62
> > Discovered open port 569/tcp on 205.217.153.62
> > Discovered open port 1763/tcp on 205.217.153.62
> > Discovered open port 61440/tcp on 205.217.153.62
> > Discovered open port 4998/tcp on 205.217.153.62
> > Increasing send delay for 205.217.153.62 from 0 to 5 due to 11 out of 24
> > dropped
> > probes since last increase.

<snip...you get the idea>

I am not using Road Runner; I have DSL from SBC.  I'm thinking SBC has
some sort of filtering in place since no symptoms occur while scaning
hosts in my LAN.  I'll tinker with various timing and parallelism
settings, maybe do some firewall evasion.

Thanks


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