Home page logo

nmap-dev logo Nmap Development mailing list archives

Re: Bug Report with jetdirect printer server
From: Brandon Enright <bmenrigh () ucsd edu>
Date: Thu, 27 Dec 2007 21:56:15 +0000

Hash: SHA1

ACK.  Most printers are junk.  We have the same problem.  Most of the
time it is caused by the "Version Scan" option (-sV) but sometimes it
is caused by the OS fingerprinting (-O[1,2]).  Rather than let crappy
printers dictate what sort of scans we do, we tell the owners to move
the printer into RFC1918 address space.

Depending on what network equipment you use, that may be easiest to do
by putting all of your printers into and then either
turning on proxy-arp on your router/NAT or opening up the mask on all
your machines to

Another option would be to maintain a printer exclude file and
then just pass --excludefile <file> to Nmap each time you run a scan.


On Thu, 27 Dec 2007 16:33:53 -0500
"Travis Austin" <travis () goabs net> wrote:

When nmap does its scan of our network it scans the jetdirect devices
and lists them correctly but after it does this scan the jetdirect
printer servers must be restarted before anything else can be
printed.  I discovered this after doing a scan on
which scanned the entire network and made this issue apparent.

The simple solution is to walk up and power cycle all the jetdirect
devices but this could be a very confusing thing to people that are
new to this.  I don't know what specifically caused the problem but I
confirmed it by running another network scan with the same end result
(no one could print)

Thanks for the great product and I hope this info is of some use to

Travis Austin

IT Manager

Anesthesia Business Solutions

Version: GnuPG v1.4.7 (GNU/Linux)


Sent through the nmap-dev mailing list
Archived at http://SecLists.Org

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]