Re: Bug Report with jetdirect printer server

[Brandon Enright <bmenrigh () ucsd edu>]

-----BEGIN PGP SIGNED MESSAGE-----
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 192.168.0.0/24 and then either
turning on proxy-arp on your router/NAT or opening up the mask on all
your machines to 255.255.254.0.

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

Brandon


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 192.168.1.0/24
> 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
> you.
>
>
> Travis Austin
>
> IT Manager
>
> Anesthesia Business Solutions
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFHdB9/qaGPzAsl94IRAtWZAJ4rigKEPeqiTCnSOeP70GE/iNcOpACcDtea
VGjVfhOOQ5Ghui8brhx7zho=
=oRnw
-----END PGP SIGNATURE-----

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org