One of the biggest things for this is *not* scanning tcp 9100 as it will
print out anything that comes in on that port.
9100 is a bad port to send to, you're right about that ;) but the crash
problems manifest most prominently on port 23. If you can bung up that
port, the whole thing is usually fairly toasted. Monolithic server/stack
code or something, I dunno.
I've actually put alot of work into solving the HP printer crashing
problem. You gotta understand you can crash these printers with
anything, IP360, nessus, nmap... hell even telnetting too many times
will do it. Upgrading both the printer firmware *and* the JetDirect
firmware does help, but it does not eliminate the problem entirely.
Shameless plug: I bitched about this very problem on our blog and gave
it to HP pretty good, I think, check it out:
http://blog.ncircle.com/archives/2005/11/vendors_please.htm#comments
HP is working on solving these problems; it's not an issue unique to our
product. HP printers are just very non-robust on the network. I've seen
similar issues with Canon. I've seen maybe a couple Lexmark lock-up bugs
in my time at the company, but whether that has to do with HP being
having more printers in the field than Lexmark does I dunno.
Cheers,
Byron
------------------------------------------------------------------------------
Audit your website security with Acunetix Web Vulnerability Scanner:
Hackers are concentrating their efforts on attacking applications on your
website. Up to 75% of cyber attacks are launched on shopping carts, forms,
login pages, dynamic content etc. Firewalls, SSL and locked-down servers are
futile against web application hacking. Check your website for vulnerabilities
to SQL injection, Cross site scripting and other web attacks before hackers do!
Download Trial at:
http://www.securityfocus.com/sponsor/pen-test_050831
-------------------------------------------------------------------------------
