We have run into this problem many times, its not actually Nessus crashing them, its Nmap and the syn-scan. There are a set of firmware revisions that rollover and die when you nmap -sS them. The actual URL lsiting the problematic versions and the fixes eludes me at the moment, but a few minutes with Google should be enough to find it. You may want to first scan the network for systems with port 9100 or 515 open and run a separate scan on those using the Nmap connect() scan option instead. Make sure to disable Nessus's bult-in portscanner as well, since it does the same thing. Another big problem with printers that they tend to print whatever you send to certain ports. The find_service plugin (and anything else that works on unknown) services will cause them to dump out garbage. This becomes a problem when those printers are full of things like bank checks :) There is an easy fix to this, but it also involves tailoring the scan parameters and some preprocessing.
On Friday 10 January 2003 01:28, Baumgartner Christoph wrote: > We made the same experience. The only solution is a reset of the HP > laser printers after they hook (it seems that HP ink-jets are not > affected). I would test the HP laser printers during working hours > because the users/super users can reset/restart the printers if they > are informed before. > > I would appreciate if the author of the plugin could fix the problem. - [EMAIL PROTECTED]: general discussions about Nessus. * To unsubscribe, send a mail to [EMAIL PROTECTED] with "unsubscribe nessus" in the body.
