Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We've upgraded some of our servers to 12.04 recently, and i've noticed that when I run nmap from some other server to check open ports on these 12.04 servers it take WAY longer than before. is this a known issue?

share|improve this question
What is the exact command you are using? Are there any new firewall rules or IDS? – Lucas Kauffman Aug 6 '12 at 8:44
Hi, thanks for your reply. You are right, it seems that nmap runs slower when all ports are filtered than when even one port is not filtered. I wonder why is that? – SecondThought Aug 6 '12 at 8:52
I'll make it an answer then ;) – Lucas Kauffman Aug 6 '12 at 8:54
what's the difference between 1000 filtered ports and 999 filtered ports that makes it so much slower?... – SecondThought Aug 6 '12 at 12:15
I haven't got an idea, what port did you leave out? – Lucas Kauffman Aug 6 '12 at 20:14
up vote 1 down vote accepted

When port filtering is enabled, nmap can run a lot slower than normal.

share|improve this answer

Nmap can adjust its timing based on round-trip times and expected responses. A port is considered filtered if no response is received within some time period. If Nmap finds a port open early in the scan, it can reduce the timeout for considering a port filtered, speeding up the rest of the scan. This is why a host with 1 open (or 1 closed) and 999 filtered ports can take significantly less time to scan than one with 1000 filtered ports.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.