Re: nmap scan results

[Jacob Bresciani <jacob () bresciani ca>]

from the man page (at least the man page on debian amd64)

The  result  of  running nmap is usually a list of interesting ports on
the machine(s) being scanned (if any).  Nmap always  gives  the  port's
"well  known"  service name (if any), number, state, and protocol.  The
state is either "open", "filtered", or "unfiltered".  Open  means  that
the  target  machine  will accept() connections on that port.  Filtered
means that a firewall, filter, or other network  obstacle  is  covering
the port and preventing nmap from determining whether the port is open.
Unfiltered means that the port is known by nmap to  be  closed  and  no
firewall/filter  seems to be interfering with nmap's attempts to deter-
mine this.  Unfiltered ports are the common case  and  are  only  shown
when most of the scanned ports are in the filtered state.

On Fri, 2005-03-18 at 14:37 -0600, Ju Ne wrote:
> I have been unhappy with many of the port scanners out there and I’m just 
> starting to learn the power of nmap.
>
> I’ve been reviewing nmap scan results on my network.  If a port comes back 
> as filtered does that mean that it is open, closed, firewalled, or just 
> unknown?
>
> ddjjembe
>
> _________________________________________________________________
> Don’t just search. Find. Check out the new MSN Search! 
> http://search.msn.click-url.com/go/onm00200636ave/direct/01/