💻 Software
Why is this NMAP scan to a remote host showing me no ports open when the ports REALLY are open?
Fresh7 days ago
Mar 15, 202618276 viewsConfidence Score0%
0%
Problem
As you can see, the above telnet command shows port 33491 is open. Running NMAP with on that same IP and port shows it as closed: In the above example, telnet shows the port open, but NMAP shows the port as 'filtered' aka closed. How can I get NMAP to show open ports for remote hosts (that disable …
Error Output
telnet 99.99.99.99 33491 Trying 99.99.99.99... Connected to 99.99.99.99.. Escape character is '^]' ^] telnet> close Connection closed.
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Canonical Fix
Unverified Fix
New Fix – Awaiting Verification
Fix for: Why is this NMAP scan to a remote host showing me no ports open when the ports REALLY are open?
Low Risk
filtered Nmap cannot determine whether the port is open because packet filtering prevents its probes from reaching the port. The filtering could be from a dedicated firewall device, router rules, or host-based firewall software. These ports frustrat…
Awaiting Verification
Be the first to verify this fix
Sign in to verify this fix