HP OfficeJet Printing

Home » CentOS » HP OfficeJet Printing
CentOS 3 Comments

There has been a bit of grumbling recently about HP printer capability in one of our smallest prototyping Labs.  We have a single GigE switch connecting a Windows 7 machine and a Dell/CentOS-6 machine.  The CentOS
machine also has connectivity via another network.  Currently, only the Windows 7 machine has been setup for printing on our HP OfficeJet 8615. Our Samba effort on the CentOS system has not been successful so we use Cygwin and ftp to move files to the Windows 7 system for printing. Being able to print directly from the CentOS 6 system would be most convenient.

Software supporting the HP OfficeJet Pro 8615 is apparently available as indicated in the links and other information below.  We also see that hplip was apparently part of an installation or update performed on the CentOS 6 Dell machine at some point in time.

http://sourceforge.net/projects/hplip/?source=typ_redirect http://hplipopensource.com/hplip-web/index.html The current version of the HPLIP solution is: 3.15.11.

[user@dell ~]$ uname -a Linux dell 2.6.32-573.12.1.el6.x86_64 #1 SMP Tue Dec 15 21:19:08 2015\
x86_64 x86_64 x86_64 GNU/Linux
[user@dell ~]$
[user@dell ~]$ rpm -qa hplip hplip-3.14.6-3.el6.x86_64
[user@dell ~]$
[user@dell ~]$ which hp-setup

/usr/bin/hp-setup

Using this open source software seems easy enough, but we have concerns about printing from the Windows 7 machine if the CentOS 6 system is setup for printing.

Is there any significant possibility that printer setup or printer use on the CentOS 6 system will negatively impact printing functionality on the Windows 7 machine?

Thanks in advance for any help or advice, and Happy New Year.

3 thoughts on - HP OfficeJet Printing

  • Why go through all this trouble when you can connect the printer to the network directly and be done with it?

    —
    Sent from the Delta quadrant using Borg technology!

    Nux!
    http://www.nux.ro

    —– Original Message —–

  • I for one do not like clients sending print jobs to printer directly. Suppose you have many clients. And one of them hits some PS implementation bug in the printer, to recover from which you have to power cycle printer. And as print job didn’t finish successfully, client re-sends it to printer after you power cycle printer, which knocks down the printer again. It will take a lot of effort to find _that_ client. I’ve been trough this once.

    I usually set up cups on UNIX or Linux (with cups-lpd, I’ve found it more robust than having clients using ipp). Cups talks to printers via jetdirect. Printers are configured to not accept connections from anything but print server. Clients connect to print server via LPD. On Windows clients I first enable two LPD related services, thus I can make Windows talk to cups server its native (LPD) language.

    Of course, if you have one machine talking to printer, then what Nux suggests makes perfect sense, why go into trouble.

    I hope, this helps.

    Valeri

    ++++++++++++++++++++++++++++++++++++++++
    Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247
    ++++++++++++++++++++++++++++++++++++++++

  • I now understand that one piece of important informationwas left out of my original posting. The printer is alreadyconnected to the same network as the Window 7 and the CentOScomputers.  Current access from the Windows 7 machine is viathe network supported by the GigE switch.

    Why go through all this trouble when you can connect the printer to the network directly and be done with it?

    —
    Sent from the Delta quadrant using Borg technology!

    Nux!
    http://www.nux.ro

    —– Original Message —–