@Su8Z3r0 said:
i’ve encountered a problem also, Does anyone know why i’m getting this error.
└──╼ [★]$ nmap 178.62.54.33
Starting Nmap 7.80 ( https://nmap.org ) at 2021-03-23 22:36 UTC
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.05 seconds
─[user106059@htb-xdfadiomy3]─[~]
└──╼ [★]$ nmap -Pn 178.62.54.33
Starting Nmap 7.80 ( https://nmap.org ) at 2021-03-23 22:36 UTC
Nmap scan report for 178.62.54.33
Host is up (0.0016s latency).
All 1000 scanned ports on 178.62.54.33 are filtered (905) or closed (95)Nmap done: 1 IP address (1 host up) scanned in 9.47 seconds
Possibly dozens of reasons. I haven’t done this lab so it is hard to guess as there isn’t much information to go on.
Filtered generally means nmap received no response, closed generally means there was an rst packet. If you know how to use wireshark/tcpdump, you could sniff the traffic and confirm this.
Try:
traceroute 178.62.54.33nmap -Pn -sC -sV -vvvvvvvvvv --reason -T4 -p- 178.62.54.33to get more information from nmap.
Its even possible the lab is configured to require you to do something differently than a simple scan.