mailing list archives
differences between nmap-online and nmap command line
From: "sara fink" <sara.fink () gmail com>
Date: Tue, 24 Jun 2008 13:43:19 +0300
I ran nmap online on my ip. I got some results. But when I run the
same nmap on my ip from command line I get totally different results.
Here are the results that I get from nmap onlline.
Nmap Options: -p1-3000 -T4 -sS xx.xx.xx.xx
Starting Nmap 4.11 ( http://www.insecure.org/nmap ) at 2008-06-24
10:47 Central Europe Daylight Time
Warning: Giving up on port early because retransmission cap hit.
Interesting ports on xx.xx.xx.xx:
Not shown: 2984 closed ports
PORT STATE SERVICE
106/tcp filtered pop3pw
135/tcp filtered msrpc
137/tcp filtered netbios-ns
138/tcp filtered netbios-dgm
139/tcp filtered netbios-ssn
382/tcp filtered hp-managed-node
403/tcp filtered decap
445/tcp filtered microsoft-ds
778/tcp filtered unknown
1033/tcp filtered netinfo
1132/tcp filtered unknown
1720/tcp filtered H.323/Q.931
2224/tcp filtered unknown
2745/tcp filtered unknown
2858/tcp filtered unknown
2947/tcp filtered unknown
Nmap finished: 1 IP address (1 host up) scanned in 587.562 seconds
When I run from command line the scanning takes less than a second. I
think it doesn't scan at all.
nmap -p1-3000 -T4 -sS xx.xx.xx.xx
Starting Nmap 4.65 ( http://nmap.org ) at 2008-06-24 13:17 IDT
All 3000 scanned ports on xx.xx.xx.xx are closed
How this can be explained?
I also have a problem on nmap-online. If I try to run ports 1-6000 or
other larger range of ports, it says the scan took too long. Is there
a possiblity to do something about it?
Sent through the nmap-dev mailing list
Archived at http://SecLists.Org
- differences between nmap-online and nmap command line sara fink (Jun 24)