On Tue, May 18, 2004 at 07:59:06AM +0100, senthil prabu wrote: > [Tue May 11 07:16:28 2004][6938] user test1 : launching ping_host.nasl > against 120.20.30.126 [6939] ... > [Tue May 11 07:16:28 2004][6938] user test1 : The remote host > (120.20.30.126) is dead
The report is empty because the "Ping the remote host" scanner failed to
detect the host was alive. What preferences are in effect for this
plugin (ie, look on the Prefs tab, under "Ping the remote host")? Is the
target listening on at least one of the port specified and are you doing
a TCP ping?
You may wish to specify the following as a port range:
21;22;23;25;53;79;80;110;113;135;139;143;264;389;443;993;1454;1723;3389;8080
It will result in slower scans but should work well with most systems.
> Suppose If I didnot enable the option,Ping the remote host,and enable
> any other 5 options given above,ie.enabling the
> TCP Connect( ) Scan option,Scanning for 120.20.30.126 goes
> well,launching all pluggins
It looks like several had not finished running. What does ps show?
> Why the Machine hangs,(even I am giving a Single IP,Nessus supposes
> to hang on HP-UX on alarger Scan)Is there any remedy to stop this
> Problem.
As Renaud suggested, you would probably be better off to switch to
another platform. I know that there are issues with HPUX and older
versions of libpcap and that Nessus by default uses an older version.
Perhaps switching to the newer version would improve things, perhaps
not.
> Also please tell me,how to changes the Scan options setting while
> testing inCommandline.
Edit the configuration file (by default ~/.nessusrc).
George
--
[EMAIL PROTECTED]
pgpEzDDoud5BY.pgp
Description: PGP signature
_______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
