Changing the RPC connect timeouts.

[patrick at aushack.com (Patrick Webster)]

Hi Jonathan,

This is just a guess. If you have a look at the SMB exceptions list the
error message "The SMB server did not reply to our request" is because there
is no SMB reply (e.g. STATUS_SUCCESS). I would assume that this is because
the exploit attacks SMB, and the SMB thread is used to run your payload
instead of the Windows SMB cleanup tasks.

Oh and have you looked at 'show advanced' for other timeout options
(WfsDelay, ConnectTimeout etc).

-Patrick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.metasploit.com/pipermail/framework/attachments/20070613/79531a18/attachment.htm>