SEO

I recently set up 4 HP2015 printers on a subnet using the hp utility in
V5.06. Apparently, the embedded print servers are not 100% compatible
with the std jetdirects. The unix host can ping them but they will not
print. There is very little documentation on the print server (ie: if
port is other than 9100). Has anyone used this printer?

Tony D wrote (on Fri, Dec 14, 2007 at 11:38:58AM -0500):
> I recently set up 4 HP2015 printers on a subnet using the hp utility in
> V5.06. Apparently, the embedded print servers are not 100% compatible
> with the std jetdirects. The unix host can ping them but they will not
> print. There is very little documentation on the print server (ie: if
> port is other than 9100). Has anyone used this printer?

No, but what I would do is put a linux box on the subnet and run nmap.
This will tell you what ports they are listening on. Depending upon the
results, you may also want to run tcpdump/ethereal to see who's saying
what.

--
_________________________________________
Nachman Yaakov Ziskind, FSPA, LLM awacs@ziskind.us
Attorney and Counselor-at-Law http://ziskind.us
Economic Group Pension Services http://egps.com
Actuaries and Employee Benefit Consultants

----- Original Message -----
From: "Nachman Yaakov Ziskind" <awacs@ziskind.us>
Newsgroups: comp.unix.sco.misc
To: <distro@jpr.com>
Sent: Friday, December 14, 2007 12:30 PM
Subject: Re: Cannot print to HP2015


> Tony D wrote (on Fri, Dec 14, 2007 at 11:38:58AM -0500):
>> I recently set up 4 HP2015 printers on a subnet using the hp utility in
>> V5.06. Apparently, the embedded print servers are not 100% compatible
>> with the std jetdirects. The unix host can ping them but they will not
>> print. There is very little documentation on the print server (ie: if
>> port is other than 9100). Has anyone used this printer?
>
> No, but what I would do is put a linux box on the subnet and run nmap.
> This will tell you what ports they are listening on. Depending upon the
> results, you may also want to run tcpdump/ethereal to see who's saying
> what.

The first thing to do is see if the thing even supports pcl5 or lower.
.... it appears to.

Looks just like a 1320, and I can say that a 1320 built-in print server works just like a standard jetdirect, in that:

* pressing the reset button (pen-hole near the network jack) briefly spits out 2 steets of setup info, including the printers current IP and what services are active. Why waste time guessing what features exist or are active?

* jetdirect and lpd and telnet and http (at least) are active by default.

* the jetdirect port is 9100 the same as for any other single-port jetdirect

* In the absense of dhcp, you can usually give it any IP you want and then telnet to it merely by knowing the MAC address printed on the sticker on the outside, which a user can read to you over the phone and you can do everything from scratch, from anywhere, just by having as little as dialup access to the sco box.
>From the sco box:
# arp -s 192.168.1.20 00:14:38:ce:0b:7b
# ping 192.168.1.20
# telnet 192.168.1.20
<configure & save ip settings permanently once telnetted in>

So why waste time guessing?
1 : print the setup sheet or do the arp/mac trick to get or set an ip.
2 : telnet or http to the thing and configure-away
3 : use printer


Next, now that you've established connectivity and service type...

Are you sure you are sending data that includes enough pcl codes to ensure the printer resets to a sane mode before the main print data? Have you tried direct tests netcat like:
echo "\033Ethis is a test\014\033E\c" |/usr/spool/lp/bin/netcat -p 9100 -h 192.168.1.104
or possibly:
echo "\033%-12345X@PCL\r\n\033Ethis is a test\r\n\014\033E\c" |/usr/spool/lp/bin/netcat -p 9100 -h 192.168.1.104

The exact netcat command syntax, binary name and path depends on the version of netcat you have installed.
Above is if you have installed this:
http://www.aljex.com/bkw/sco/#rlpnc

There are only about 25 other ways you might deliver raw tcp depending on what stuff you have installed and how comfy you are in various scripting languages that have tcp commands built in or loadable in a module.

Does that get you going?

Brian K. White brian@aljex.com http://www.myspace.com/KEYofR
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!

Brian K. White wrote:
> ----- Original Message -----
> From: "Nachman Yaakov Ziskind" <awacs@ziskind.us>
> Newsgroups: comp.unix.sco.misc
> To: <distro@jpr.com>
> Sent: Friday, December 14, 2007 12:30 PM
> Subject: Re: Cannot print to HP2015
>
>
>> Tony D wrote (on Fri, Dec 14, 2007 at 11:38:58AM -0500):
>>> I recently set up 4 HP2015 printers on a subnet using the hp utility in
>>> V5.06. Apparently, the embedded print servers are not 100% compatible
>>> with the std jetdirects. The unix host can ping them but they will not
>>> print. There is very little documentation on the print server (ie: if
>>> port is other than 9100). Has anyone used this printer?
>> No, but what I would do is put a linux box on the subnet and run nmap.
>> This will tell you what ports they are listening on. Depending upon the
>> results, you may also want to run tcpdump/ethereal to see who's saying
>> what.
>
> The first thing to do is see if the thing even supports pcl5 or lower.
> ... it appears to.
>
> Looks just like a 1320, and I can say that a 1320 built-in print server works just like a standard jetdirect, in that:
>
> * pressing the reset button (pen-hole near the network jack) briefly spits out 2 steets of setup info, including the printers current IP and what services are active. Why waste time guessing what features exist or are active?
>
> * jetdirect and lpd and telnet and http (at least) are active by default.
>
> * the jetdirect port is 9100 the same as for any other single-port jetdirect
>
> * In the absense of dhcp, you can usually give it any IP you want and then telnet to it merely by knowing the MAC address printed on the sticker on the outside, which a user can read to you over the phone and you can do everything from scratch, from anywhere, just by having as little as dialup access to the sco box.
>>From the sco box:
> # arp -s 192.168.1.20 00:14:38:ce:0b:7b
> # ping 192.168.1.20
> # telnet 192.168.1.20
> <configure & save ip settings permanently once telnetted in>
>
> So why waste time guessing?
> 1 : print the setup sheet or do the arp/mac trick to get or set an ip.
> 2 : telnet or http to the thing and configure-away
> 3 : use printer
>
>
> Next, now that you've established connectivity and service type...
>
> Are you sure you are sending data that includes enough pcl codes to ensure the printer resets to a sane mode before the main print data? Have you tried direct tests netcat like:
> echo "\033Ethis is a test\014\033E\c" |/usr/spool/lp/bin/netcat -p 9100 -h 192.168.1.104
> or possibly:
> echo "\033%-12345X@PCL\r\n\033Ethis is a test\r\n\014\033E\c" |/usr/spool/lp/bin/netcat -p 9100 -h 192.168.1.104
>
> The exact netcat command syntax, binary name and path depends on the version of netcat you have installed.
> Above is if you have installed this:
> http://www.aljex.com/bkw/sco/#rlpnc
>
> There are only about 25 other ways you might deliver raw tcp depending on what stuff you have installed and how comfy you are in various scripting languages that have tcp commands built in or loadable in a module.
>
> Does that get you going?
>
> Brian K. White brian@aljex.com http://www.myspace.com/KEYofR
> +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!

I have connectivity to the printers. They are set to fixed ip addresses.
The embedded jet direct does not support telnet, but you can bring it
up via browser but it does not show the port (just clutching at straws
there). Netcat was installed by one of our applications. I found it and
the above test works, so they use the std hp port. I've never used
netcat because all of our print servers are std jetdirects and the
system hp utility always worked just fine. Time for more research.

> I have connectivity to the printers. They are set to fixed ip addresses.
> The embedded jet direct does not support telnet, but you can bring it
> up via browser but it does not show the port (just clutching at straws
> there). Netcat was installed by one of our applications. I found it and
> the above test works, so they use the std hp port. I've never used
> netcat because all of our print servers are std jetdirects and the
> system hp utility always worked just fine. Time for more research.

From SCO server, telnet to printerver on port 9100. Type hello, then
close the telnet connection (crtl-]). If the printer prints what
you've typed, you have good network connectivity between the hosts and
the printer is accepting jobs on 9100. The problem may be the printer
doesn't fully support the HP jetdirect command set. I think the hpnp
executable checks for paper status and other things before sending the
job, and if it doesn't like what it sees, it punts and doesn't send
the job. Assuming the telnet test above worked, you can substitute
ncat for hpnp .. that tony lawrence fella has instructions on his page
(aplawrence.com). This is also the case if you want to use non-HP
printers that still listen on 9100.

Or you could set up an LPR queue to it, but I find the 9100 method is
easier to deal with and works fine with ncat.