use of meterpreter (copy for the list )

[thomas.werth at vahle.de (Thomas Werth)]

so i did two more tests.
First i tried to proxy a ssh connection via exploitet proxy host. This
works very well.
Then i tried to run an attack again through this proxy. i delayed
creating forward of port 4444 til connected msg appears.
I'm running actual msf under win32. Now i got an error Msg that differs
from all other. here's the log :

msf msrpc_dcom_ms03_026(win32_bind) > exploit
[*] Starting Bind Handler.
[*] Connected to REMACT with group ID 0x0
[*] Got connection from 127.0.0.1:2197 <-> 127.0.0.1:4444
Can't locate object method "HandleConsole" via package
"Msf::Payload::win32_bind
" at /home/framework/lib/Msf/PayloadComponent/ConnectionHandler.pm line 61.



mmiller at hick.org schrieb:
> On Mon, Apr 18, 2005 at 10:07:48AM +0200, Thomas Werth wrote:
>
> > > Does the bind handler ever say it established the connection?  Does it
> > > say this before or after the 'Connected to REMACT'?  If it says that the
> > > bind handler has established the connection before the 'REMACT' line
> > > then you may have created the port forward too soon.  Can you include
> > > the full output from the exploit command?
> >
> > bind handler doesn't say it establishes a connection. Just saw that on
> > meterpreter window an error is thrown up open_tcp_channel: failure, 10061.
>
>
> The above error code indicates why it's not working.  10061 is
> WSACONNREFUSED.  This means that when the meterpreter server instance
> attempted to connect to 10.10.10.77 on port 135 (or 4444 depending on
> the stage), the connection was refused.  This is probably indicative of
> the fact that the exploit did not work against the machine that you are
> attempting to target.  Are you certain that it's vulnerable?