Re: nmap results filtered

Also, it doesn;t come back with filtered for all of the other ports that
aren't allowed through ( I'm scanning 65000 ports )

"news.so-net.com.hk" <xxx@xxx.com> wrote in message
news:3f4f5fb8@shknews01...
> Hi,
>
> I'm just wondering if anyone has come across this.
> I am using nmap to scan a number of hosts.
> The firewall is setup to drop all port access except 80 and 443.
> The results from the -sS and -sT scans are the same.
> Does anyone know why it is listing some of the ports as filtered even
though
> these as supposed to be dropped by the firewall.
>
> Port State Service
> 80/tcp open http
> 135/tcp filtered loc-srv
> 139/tcp filtered netbios-ssn
> 443/tcp open https
> 445/tcp filtered microsoft-ds
> 593/tcp filtered http-rpc-epmap
> 1720/tcp filtered H.323/Q.931
>
>

news.so-net.com.hk wrote:
> Also, it doesn;t come back with filtered for all of the other ports
> that aren't allowed through ( I'm scanning 65000 ports )

Filtered usually means stuff that is filtered by the Internet Service
Provider before it even gets to the machine that you're nmap-ing.

if you use DROP and nmap see what host is up
it expect to recive ICMP:port unrechable
so mark it port as filtered

Durk van Veen wrote:
> news.so-net.com.hk wrote:
>
>>Also, it doesn;t come back with filtered for all of the other ports
>>that aren't allowed through ( I'm scanning 65000 ports )
>
>
> Filtered usually means stuff that is filtered by the Internet Service
> Provider before it even gets to the machine that you're nmap-ing.
>
>