0

I keep getting this when I start to exploit, trying to exploit my xp machine but this keeps happening, I can not find the fix anywhere, I don't believe I am the only one getting this.. I am a beginner, just putting it out there.

msf exploit(ms08_067_netapi) > exploit

[*] Started reverse handler on 192.168.47.129:4444

[-] Exploit failed [unreachable]: Rex::ConnectionTimeout The connection timed out (192.168.47.131:445).

I followed this video https://www.youtube.com/watch?v=6WMbrcGzNbk

2

You asked this question and it was downvoted before. There could be a lot of reasons for this happening, your question is too broad, and lacks a lot of relevant information. For example, can you ping that host, is it running a firewall, it is vulnerable to that exploit. What you are experiencing is the host not responding back after it is exploited. This could be because of a firewall on either end (the attacking machine, the exploited machine). I would start with firewalls since the connection is timing out. From there I would move and set a different "LPORT" since metasploit tends to act quirky at times. E.g., set LPORT 2468. If that doesn't work, then jump on the metasploit forum and ask there, you'll likely get an accurate explanation.

  • Sorry, and yes I know, I asked this question before but didn't make a whole lot of sense. Thank you anyway – This Is Edis Mehmedovic Nov 23 '14 at 16:47
  • 'metasploit tends to act quirky at times' -- this is the key =) msfconsole restart helped in my case. – golem Mar 22 '15 at 3:15
0

most probably a firewall.

a good firewall will block outgoing connections, just like most firewalls block incoming connections

if the local firewall does not allow outgoing connections to port 4444 that wont work

perhaps try using a basic port like 80 or 443

0

I had the same issue before. It turned out that the culprit was that specific port on the remote host is in use.

My workaround at the time was rebooting the remote machine. This can happen when you have previously opened a session and the port is still in LISTEN mode.

0

I have a similar issue , The problem was with lhost and Lport Use

Set LHOST 'attacker ip'

Set LPORT 'port number'

This may solve your issue

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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