HOSTS SEEMS DOWN

HTB Content Machines
, ,
1

I am new to here PLEASE HELP
As many time i am scanning a maching getting the same response

root@abhi:~# nmap -p- -A -T4 10.10.10.198
Starting Nmap 7.80 ( https://nmap.org ) at 2020-09-03 13:58 IST
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 2.50 seconds

Here is how my active machines page looks like

2

@mysterious72 said:

I am new to here PLEASE HELP

Are you connected via the VPN?

3

@TazWake yes i am connected

4

@mysterious72 said:

@TazWake yes i am connected

Ok next question, what is your HTB IP address?

5

I have the same problem, VPN connection is established but can not preform nmap scan, same message “host seems done”

6

@RelyingArt said:

I have the same problem, VPN connection is established but can not preform nmap scan, same message “host seems done”

  1. are you on free or VIP?
  2. what host are you trying to hit?
  3. what is your HTB IP address?
7

PING 10.10.10.27 (10.10.10.27) 56(84) bytes of data.
From 10.10.14.1 icmp_seq=1 Destination Host Unreachable
From 10.10.14.1 icmp_seq=2 Destination Host Unreachable
From 10.10.14.1 icmp_seq=3 Destination Host Unreachable
From 10.10.14.1 icmp_seq=4 Destination Host Unreachable
From 10.10.14.1 icmp_seq=5 Destination Host Unreachable
From 10.10.14.1 icmp_seq=6 Destination Host Unreachable

Free user with two hours on the PWNBOX.

8

@RelyingArt said:

PING 10.10.10.27 (10.10.10.27) 56(84) bytes of data.
From 10.10.14.1 icmp_seq=1 Destination Host Unreachable
From 10.10.14.1 icmp_seq=2 Destination Host Unreachable
From 10.10.14.1 icmp_seq=3 Destination Host Unreachable
From 10.10.14.1 icmp_seq=4 Destination Host Unreachable
From 10.10.14.1 icmp_seq=5 Destination Host Unreachable
From 10.10.14.1 icmp_seq=6 Destination Host Unreachable

Free user with two hours on the PWNBOX.

Ok - I dont know how pwnbox works.

It looks like you are trying to hit CALAMITY - I dont think that is up on the free servers unless it’s different on Pwnbox.

9

Its mentioned as target IP @ starting point section enumeration, at the end you can submit a flag. If i’m correct you have to be VIP to obtain the flag?

10

@RelyingArt said:

Its mentioned at target IP @ starting point section enumeration, ad the end you can submit a flag. If i’m correct you have to be VIP to obtain the flag?

Ok - this might be the source of the problem. From what I can see - and just testing - the Pwnbox uses your normal VPN.

I’ve just started a Pwnbox instance and then started CALAMITY and nmap worked fine, but it hit CALAMITY not ARCHETYPE.

11

I think you are correct, CALAMITY IP 10.10.10.27 is one of the retired machines, you need a VIP acces for this one.

12

Yeah - so I dont know how you get Pwnbox to connect to your starting point network.

13

Login to the HTB site via PWNbox and then downloading the startingpoint VPN file

14

cool - good plan

15

Hi, I’m having a similar issue. I’m trying to access Lame (10.10.10.3), I’m VIP, the box is active, I can successfully ping the machine but nmap says the host is down. Same with other boxes. Any suggestions?

16

Type your comment> @emilyj27 said:

Hi, I’m having a similar issue. I’m trying to access Lame (10.10.10.3), I’m VIP, the box is active, I can successfully ping the machine but nmap says the host is down. Same with other boxes. Any suggestions?

nmap -Pn

17

Type your comment> @LMAY75 said:

Type your comment> @emilyj27 said:

Hi, I’m having a similar issue. I’m trying to access Lame (10.10.10.3), I’m VIP, the box is active, I can successfully ping the machine but nmap says the host is down. Same with other boxes. Any suggestions?

nmap -Pn

Thanks. I’ve tried that earlier and it does work but I don’t think I should have to be doing that?
A separate issue is that the version of the vulnerable software on the box is different to that in any walkthroughs. The Metasploit exploit listed in the walkthrough fails to work, seemingly because of this.

18

@emilyj27 said:

Any suggestions?

Its really down to network troubleshooting.

Have you tried tracert/traceroute? Alternatively make sure it has activated properly and isn’t broken.

A separate issue is that the version of the vulnerable software on the box is different to that in any walkthroughs.

That shouldn’t happen. There isn’t normally a process to patch/upgrade software on boxes unless it generates an unexpected bug.

At this point, if you are confident that this is the case, I’d be tempted to either reboot the box or report it to HTB via a JIRA ticket.

19

Type your comment> @emilyj27 said:

Type your comment> @LMAY75 said:

(Quote)
Thanks. I’ve tried that earlier and it does work but I don’t think I should have to be doing that?
A separate issue is that the version of the vulnerable software on the box is different to that in any walkthroughs. The Metasploit exploit listed in the walkthrough fails to work, seemingly because of this.

There are no issues with the Pn flag.

As for the vuln service being different that is an issue. Maybe try to contact support.

20

@LMAY75 said:

There are no issues with the Pn flag.

I agree - and I nearly always use it because there is normally no point doing a ping on HTB. However, I dont think it will solve the problem here. If the box responds to ping but not the scans then skipping the ping probably wont make it respond.

(And, yes, there are situations where it might but I’ve never seen one on HTB :smile: )