Nessus 4 & Backtrack 4 final

[Soultaker666]

I am having issues installing Nessus 4 on BT4 Final. I have a dual boot configuration with Win7. I followed this great tutorial Installing Nessus on BT4 - Offensive Security but for some reason am unable to get the client to connect properly. I went into the nessusd.conf file and found that it is running on ports 1243 for client and ports 8834 for web. I am able to connect to the web version but not the client. The client tells me that host may not be running. I then ran an nmap scan of

nmap -p1243 127.0.0.1

and the port came up as closed. I am not sure if there is a firewall on by default with BT4 but I have not enabled one. Also, some other things that I have tried are

ifconfig lo down
ifconfig lo up

I have also restarted the Nessus server, stopped the server and started the server. I tried all three as I did not know if the restart was working properly. If anyone has any solutions for this I would greatly appreciate it. Thanks for looking.

[relaxo]

hi,
i have the same problem stuck at this connection problem

google says that u have to generate the SSL cert and use it under connection -> edit -> ssl setup
i created the ssl thing with

/opt/nessus/sbin/nessus-mkcert

and entered some figures but i didnt manage it to work either

plz help
atm stick in metasploit unleashed and cant go furhter^^

[sickness]

Why use nessus when you have OpenVAS in BT4, you have the necessary tutorials and information to configure it ...

[dustyboner]

start the nessus server

/etc/init.d/nessusd start

open your web browser and use the address:
https://xxx.xxx.xxx.xxx:8834
where xxx.xxx.xxx.xxx is your lan ip.

like https://192.168.1.123:8834

[Xortor]

Why use nessus when you have OpenVAS in BT4, you have the necessary tutorials and information to configure it ...

Because there's more than one way to skin a cat.

[jpkirk]

start the nessus server

/etc/init.d/nessusd start

open your web browser and use the address:
https://xxx.xxx.xxx.xxx:8834
where xxx.xxx.xxx.xxx is your lan ip.

like https://192.168.1.123:8834

I believe the original poster noted he could connect with the web client. He wanted to connect the old way, with the Nessus client. I did not try that because, well, the new web interface seems to work fine for me. I rather like it. Maybe this weekend I'll give it a go.

So, doing a little reading before I jump into installing the old client....

The Nessus User Guide states....

In addition to the Nessus GUI, Tenable supports two other methods for communicating with
the Nessus server: the Unix command line interface and the Security Center.

So... the old client is out, the new web client is in. I like the new web client, so will not be beating my head against the wall for the old client. YMMV. Let other fun commence .... now!