Re: Remote host dead?

On Jun 23, 2008, at 6:39 PM, Roman Medina-Heigl Hernandez wrote:

> Btw, the "do not scan fragile
> devices" will only appear if you create a new policy. Why doesn't it  
> appear
> when editing default scan policy?

It's a known issue, I'm afraid.

> I disabled the ping scan and it didn't work either. But... I  
> reenabled ping
> and check icmp ping in advanced options, and now it worked!! I  
> suppose that
> Nessus marks a host as dead if all tests failed, and now that icmp  
> ping is
> being checked, the host is no longer mark as dead... is it right?
>
> Anyway, I'm still a bit confused because letting only marked the  
> "Nessus
> TCP scanner" option (thus ping scanner disabled), and changing "port
> scanner range" from "default" to 1-65535, the host is still being  
> marked as
> dead. What's the exact algorithm to mark a host as dead?

Hmm, my advice wasn't totally correct. If you're enabling plugin  
dependencies (which you almost certainly want to do), ping_host.nasl  
will get run anyway. The correct solution for disabling the ping  
scanner is to uncheck all the boxes (ICMP ping, TCP ping, and ARP ping).

> And why are those
> ports not being used by TCP scanner?

Are you scanning over a PPP or PPTP connection? That's also not  
supported currently in Nessus Windows.


George
-- 
theall@tenablesecurity.com



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