Metasploit mailing list archives

Re: nessus_connect error...


From: anil saini <imanilsaini () gmail com>
Date: Fri, 1 Oct 2010 13:55:08 +0530

Thanks
             I got it going by installing nessus 4.2 and port 8834.


For a new scan command is:-

 *nessus_scan_new <policy id> <scan name> <targets>
*

But *nessus_policy_list* command on my computer returns nothing.


msf exploit(handler) > nessus_policy_list
[+] Nessus Policy List

ID  Name  Owner  visability
--  ----  -----  ----------

msf exploit(handler) >


*What is the command to create new nessus_policy*?
In Nessus GUI Client it is very easy but what is the command to create it
from msf .





On Fri, Oct 1, 2010 at 1:09 PM, Vlatko Kosturjak <kost () linux hr> wrote:

On 10/01/2010 07:46 AM, anil saini wrote:
I am not able to connect to my nessus server.
My nessus server ip is 192.168.1.135 and running on nessus default port
1241.
user name and password -> meta
I am getting the following error.

msf exploit(handler) > nessus_connect meta:meta@192.168.1.135:1241
<http://meta:meta@192.168.1.135:1241> ok
[*] Connecting to https://202.54.98.135:1241/ as meta
[-] Error while running command nessus_connect: undefined method
`print_error' for #<NessusXMLRPC::NessusXMLRPC:0x7f8092f85d58>

Anil,

You're talking XMLRPC protocol which is http based (usually 8834 port)
on NTP port (1241) which is socket based. They are too different
protocols and ports. You should have Nessus 4.2 or higher and then try
to specify XMLRPC port (8834).

AFAIK, NTP protocol will soon become obsolete in Nessus and it is
superseeded by XMLRPC.

Kost

_______________________________________________
https://mail.metasploit.com/mailman/listinfo/framework

Current thread: