Hi Sergio, Is this device a printer?
What was your previous version of Nessus? And lastly, can you try disabling "don't scan printers" and "don't scan fragile devices"? Ron Gula Tenable Network Security Sergio Castro wrote: > Hi Ron, > > I just checked scan.log. I have this: > -------------------------------------------------------- > [Mon Jun 09 12:44:39 2008][2804] Use default port range > [Mon Jun 09 12:44:46 2008][2804] user zerge : testing www.unicin.net > (200.57.93.68) [2804] > [Mon Jun 09 12:44:46 2008][2804] Scan 200.57.93.68 using 20201 plugins > [Mon Jun 09 12:44:46 2008][2804] user zerge : launching > clrtxt_proto_settings.nasl against 200.57.93.68 [1] > [Mon Jun 09 12:44:46 2008][2804] user zerge : launching > dont_scan_settings.nasl against 200.57.93.68 [2] > [Mon Jun 09 12:44:46 2008][2804] user zerge : launching ssh_settings.nasl > against 200.57.93.68 [3] > [Mon Jun 09 12:44:46 2008][2804] clrtxt_proto_settings.nasl (process 1) > finished its job against 200.57.93.68 in 0.000 seconds > [Mon Jun 09 12:44:46 2008][2804] dont_scan_settings.nasl (process 2) > finished its job against 200.57.93.68 in 0.000 seconds > [Mon Jun 09 12:44:46 2008][2804] ssh_settings.nasl (process 3) finished its > job against 200.57.93.68 in 0.000 seconds > [Mon Jun 09 12:44:46 2008][2804] user zerge : launching snmp_settings.nasl > against 200.57.93.68 [4] > [Mon Jun 09 12:44:50 2008][2804] snmp_settings.nasl (process 4) finished its > job against 200.57.93.68 in 3.234 seconds > [Mon Jun 09 12:44:50 2008][2804] user zerge : launching ping_host.nasl > against 200.57.93.68 [5] > [Mon Jun 09 12:44:53 2008][2804] ping_host.nasl (process 5) finished its job > against 200.57.93.68 in 3.015 seconds > [Mon Jun 09 12:44:53 2008][2804] user zerge : launching > dont_scan_printers.nasl against 200.57.93.68 [6] > [Mon Jun 09 12:44:53 2008][2804] The remote host (200.57.93.68) is dead > [Mon Jun 09 12:44:53 2008][2804] Finished testing 200.57.93.68. Time : 6.421 > secs, 6 plugins launched > [Mon Jun 09 12:44:53 2008][2804] 1 hosts scanned > -------------------------------------------------------- > > Note the "remote host is dead". I know as a fact that it is not, and I used > to scan this host just fine with the previous version of Nessus. > I just scanned other hosts, and get the same "remote host is dead" response. > My firewall and antivirus are off. When on, they don't affect local network > scans. > The host is a Linux server. No idea why "dont_scan_printers.nasl" is being > launched. > I believe the previous Nessus version I was using was 3.0.6. > > Thanks > > -----Mensaje original----- > De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > En nombre de Ron Gula > Enviado el: Lunes, 09 de Junio de 2008 02:37 p.m. > Para: [email protected] > Asunto: Re: Cannot scan public IPs > > Are there any local firewalls or anti-virus software on the Windows XP > machine you are running Nessus on? Have you looked at the event log for any > error or warning messages? What previous version of Nessus were you using? > > Ron Gula > Tenable Network Security > > Sergio Castro wrote: >> Hi, >> >> Yes, I should've given more detail. >> Indeed, looking at windump, I can see that during public IP scannings, >> there are no packets leaving or entering my machine. If I try a scan >> on the LAN, I can see them. >> The setup I have is identical to when I was using the previous Nessus >> version. There is no firewall or router to get in the way. >> I tried reinstalling 3.2.1, and the problem persists. >> Thanks for your help >> >> -----Mensaje original----- >> De: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] >> En nombre de Ron Gula >> Enviado el: Lunes, 09 de Junio de 2008 07:06 a.m. >> Para: undisclosed-recipients: >> CC: [email protected] >> Asunto: Re: Cannot scan public IPs >> >> Nessus does not have anything that limits which IPs you can scan. >> >> There is not enough information in your email to try for a diagnosis, >> but if you tried to sniff the session where you can't scan computers >> off of the local network, you could see if they were getting out of >> your XP computer or being stopped by a firewall, router, .etc along the > way someplace. >> Ron Gula >> Tenable Network Security >> >> Sergio Castro wrote: >>> Hi, >>> >>> I just upgraded to 3.2.1 on Windows XP; I can scan local network IPs >>> just fine, but not public IPs. I didn't have this problem in the >>> previous version. >>> Any ideas on how to fix this? >>> >>> Thanks in advance for your help >>> >> _______________________________________________ >> Nessus mailing list >> [email protected] >> http://mail.nessus.org/mailman/listinfo/nessus >> >> __________ NOD32 3167 (20080609) Information __________ >> >> This message was checked by NOD32 antivirus system. >> http://www.eset.com >> >> >> > > _______________________________________________ > Nessus mailing list > [email protected] > http://mail.nessus.org/mailman/listinfo/nessus > > __________ NOD32 3167 (20080609) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com > > > _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
