<br><font size=2><tt>nessus-bounces@list.nessus.org wrote on 10/19/2004
01:12:22 PM:<br>
> > I'm running a scan against a rather large subnet of Windows desktops.<br>
> > However, several network printers are also on this subnet. When
one of<br>
> > these printers gets hit, it prints out about 10 pages of garbage
data.<br>
> ><br>
> > I searched through the archives and found several mentions of
this in the<br>
> > past, but I didn't see a solution for it. Has anyone come
up with a good<br>
> > way to stop this from happening?<br>
> <br>
> Evade the printers. Adding them as restricted hosts in your rules
could be<br>
> one way but you must do this through manual labor.<br>
> <br>
</tt></font>
<br><font size=2 face="sans-serif">Well, that's one option that I certainly
thought of, however we probably have about 40 printers on this subnet (it's
a 22-bit subnet). Tracking down the IP address for each and every
printer would be rather difficult.</font>
<br>
<br><font size=2 face="sans-serif">I just recently picked up new the Nessus
book, and it says that "Nessus now incorporates a test to specifically
detect whether the IP being scanned is a printer, and, if this is the case,
prevent the scan from testing that IP's printing-related ports." Obviously
that's not happening in this case, but the capability must exist, right?
Is there any special configuration that needs to be done to make
this work?</font>
<br><font size=2 face="sans-serif"><br>
--<br>
Jared Breland</font>