Nmap says ports on lame are filtered, but they actually arent?

So when i scan first 1000 ports like this:
[email protected]:~ $ sudo nmap -sV -O -Pn 10.10.10.3

nmap tells me all ports are filtered:

Nmap scan report for 10.10.10.3
Host is up (3.0s latency).
All 1000 scanned ports on 10.10.10.3 are filtered
Too many fingerprints match this host to give specific OS details

OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 163.16 seconds

But when i scan a single port:

[email protected]:~ $ sudo nmap -sV -O -Pn -p139 10.10.10.3

I get the usual:

Host is up.

PORT STATE SERVICE VERSION
139/tcp filtered netbios-ssn
Too many fingerprints match this host to give specific OS details

OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 15.49 seconds

Can anyone pls help me understand why this is happening? I am scanning lame from the beginner track..... thnx alot :smile:

Comments

  • I was having a similar problem on Legacy, I hate to say this... but have you tried turning the retired machine off on the HTB site, wait like 2 minutes and then turn it back on and reconnect? I wasted like 4 hours earlier without resetting the full connection. Hopefully that helps you.

    initDr

  • AH! machine rest... it worked!! thnx alot

  • You're welcome physiocracy

    initDr

Sign In to comment.