RE: Scan Issue

But I stopped the scan after almost 15 hours: do you think if I would have
waited longer, the test could have been completed??!

Also, if I deselect Nmap, how do I cover the UDP port scanning

Thanks,

Bilal
-----Original Message-----
From: Michel Arboi [mailto:mikhail@nessus.org] 
Sent: Thursday, June 23, 2005 11:10 AM
To: Nasrallah, Bilal [CAR:1229:EXCH]
Cc: Nessus@list.nessus.org
Subject: Re: Scan Issue


On Thu Jun 23 2005 at 16:59, Bilal Nasrallah wrote:

> I am running a scan against a network device and have noticed that 
> when I select Nmap (NASL Wrapper) from Scan Options (Port scanner), 
> the scan hangs.

IMHO, it did not hang, it is just awfully slow.

> The options that I have selected under Port scanner are: Nmap, Exclude 
> toplevel domain wildcard host, Nessus TCP scanner, and Ping the remote 
> host. When I deselected the Nmap option, the scan worked just fine. 
> Any thought would highly appreciated.

You found the solution by yourself: deselect Nmap.

I suspect that the timing options are badly broken in the last version(s). A
couple of days ago, I scanned a friend machine. 
nessus_tcp_scanner was four time quicker: 
380 s with nessus_tcp_scanner, 1500+ s with nmap -T 4 ("aggressive"
timing) 

Maybe we should add --host_timeout when we launch Nmap?
e.g., if thourough_tests are disabled, we give it only half an hour to
perform the job. Anybody against this?

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus