Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: After a scan... host is considered as dead. |
|---|---|
| Date: | Tue, 8 Apr 2008 16:58:39 +0200 |
In my situation, after had disabled the ping, i can do the scan on the machine...the server machine is running FreeBSD. On Tue, Apr 8, 2008 at 4:32 PM, Steve Royer <sref007@gmail.com> wrote:
Hello everyone, Francesco Sottini post a message recently.. I have a similar problem. Consider a host A (Windows XP) and a nessus server B (installed on Windows XP). For the 1st scan of A, everything work correctly... (B ping A and A ping B) But subsequently scan of A give me alway the same result "Remote host is considered as dead..." I've force Nessus to disable pinging but the result remain the same... Within a shell on B, I cannot ping A and within a shell on A I cannot ping B (100% packet loss). In fact, on A I can ping every server on my network exept where was coming the first scan (Nessus server) And on B I can ping every workstation that have'nt been scanned. I'm using Nessus 3.2.0. This was a scenario where Nessus server is installed on Windows XP. The same result occur for the new Nessus Server rpm 3.0.6 on redhat. Thank you Steve**>* On Apr 8, 2008, at 1:57 PM, francesco sottini wrote: *>* *>* > Dears, *>* > *>* > I am doing an university project and the final goal is to scan 4 *>* > hosts and report all the problems that we meet. *>* > Well, the 4 hosts are on a private network. to scan them, we have to *>* > connect with the nessus client to a nessus server and then scan the *>* > target. *>* > The problem is that for an host, i obtain always the result:" The *>* > remote host is considered as dead - not scanning". *>* > *>* > I suppose that on that host, declared fromt he professor "an hard *>* > challenge", there is a kind of IDS or honeypot.. *>* > *>* > what can i do? *>* *>* You can force Nessus to disable pinging the remote host prior to *>* scanning. Edit your policy -> advanced -> "Ping the remote host" and *>* uncheck all the boxes (ICMP ping, TCP ping and ARP ping). * _______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
-- Francesco S.
_______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | After a scan... host is considered as dead., Steve Royer |
|---|---|
| Next by Date: | setsid() function call vulnerability (VU#740619) on OpenVMS, Yanyan Wang |
| Previous by Thread: | After a scan... host is considered as dead., Steve Royer |
| Next by Thread: | Re: After a scan... host is considered as dead., Steve Royer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |