Nmap Development mailing list archives

Re: Request for testing of HP PJL service probe


From: David Fifield <david () bamsoftware com>
Date: Thu, 15 Oct 2009 13:09:08 -0600

On Mon, Oct 12, 2009 at 11:18:52PM -0500, Vijay Sankar wrote:
Good day,

I did a regular ./configure, gmake, and sudo gmake install on OpenBSD  
4.5 -stable.

.
.
.
running install_data
running install_egg_info
NMAP SUCCESSFULLY INSTALLED

Tried the following against a Brother 5250N Printer

server11$ nmap --allports --datadir . -PS9100-9107 -sV -p 9100-9107  
10.0.0.51

Starting Nmap 5.00 ( http://nmap.org ) at 2009-10-12 22:56 CDT
Interesting ports on printer1.sankars.local (10.0.0.51):
PORT     STATE  SERVICE    VERSION
9100/tcp open   jetdirect?
9101/tcp closed jetdirect
9102/tcp closed jetdirect
9103/tcp closed jetdirect
9104/tcp closed jetdirect
9105/tcp closed jetdirect
9106/tcp closed jetdirect
9107/tcp closed jetdirect

Service detection performed. Please report any incorrect results at  
http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 122.89 seconds

After the scan, the printer started printing pages -- most of the pages  
have some gibberish, but some are blank. I turned off the printer and  
restarted it and then was able to send real print jobs.

You have to do this with a more recent version than 5.00--the special
PJL service probe was only added with r15334 on August 27, 2009. There's
a good chance it will work against this printer.

I tried the same against an HP OfficeJet Pro 7780 printer and got the  
following results.

server11$ nmap --allports --datadir . -PS9100-9107 -sV -p 9100-9107  
10.0.0.56

Starting Nmap 5.00 ( http://nmap.org ) at 2009-10-12 23:00 CDT
Note: Host seems down. If it is really up, but blocking our ping probes,  
try -PN
Nmap done: 1 IP address (0 hosts up) scanned in 3.08 seconds

The printer was up during this time and I am not sure why the scan is  
not working (pings etc. work)

If you port scan it, are any of the ports in the range 9100-9107 open?
Maybe that printer doesn't support this particular protocol.

David Fifield

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


Current thread: