Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • Did you read this solution from the Unix & Linux portal? Commented Mar 28, 2018 at 20:21
  • 1
    I actually came across this posting, but did not find it valuable. While the question is essentially identical to mine, the responses do not address the question. He asks: If it's normal to see 21,25 and 1863 as "filtered", then why aren't all the other ports appearing as "filtered" too!? This is my question. Commented Mar 28, 2018 at 20:41
  • 1
    Even the official explanation on NMAPs website does not address this question: filtered : Nmap cannot determine whether the port is open because packet filtering prevents its probes from reaching the port. In my scenario, NMAP cannot determine whether ports 1, 2, 3, 4, 5 ,6 etc etc are open, because a packet filtering device blocks the probes, yet...we do not see all these ports listed in the output as filtered. Commented Mar 28, 2018 at 20:45
  • 4
    Add --reason -v to your scan to see why Nmap chose each port state. filtered can mean "no response" but it can also mean "ICMP Admin Prohibited" and a few other ICMP codes. What is on the line that starts with "Not shown:" ? Commented Mar 29, 2018 at 3:02