RE: Zenmap Problem

["Rob Nicholls" <robert () robnicholls co uk>]

Hi David,

You're right, it's something I regularly see if I scan the entire local
subnet and don't try to exclude myself. If I'm doing the default port range
I end up with a very long scan report full of "unknown" ports for my host
that gets in the way of the handful of ports I want to read about for the
rest of the subnet.

It's probably non-trivial, but would it be possible or preferable for Nmap
to omit/skip the scan report for the localhost? If it's skipped because
"Skipping SYN Stealth Scan against 192.168.1.16 because Windows does not
support scanning your own machine (localhost) this way" then it's always
going to show "unknown" for every port.

Rob

-----Original Message-----
From: nmap-dev-bounces () insecure org [mailto:nmap-dev-bounces () insecure org]
On Behalf Of David Fifield
Sent: 24 July 2010 20:54
To: Queen9302
Cc: nmap-dev () insecure org
Subject: Re: Zenmap Problem

On Fri, Jul 23, 2010 at 09:49:29PM +0000, Queen9302 wrote:
> Hi and thanks for your helpful utility.  I downloaded the windows
automatic installer version.  I did a quick scan on my localhost.  On the
Nmap Output tab, the STATE status for each port listed is not shown.  It
only says "unknown".  Is there a fix for this?
> PORT      STATE   SERVICE
>
> 7/tcp     unknown echo
>
> 9/tcp     unknown discard
>
> 13/tcp    unknown daytime
>
> 21/tcp    unknown ftp

I think this is because Windows doesn't support a SYN scan against
localhost. If you look up higher in the output, you may see a line to
that effect. It may work if you use the -sT option for a connect scan.

David Fifield
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/


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