UNIX Printing Problem

[Jason Nickelson_1]

We've obtained a new (new to us) K260 for our test box. I installed the server from scratch with HPUX 11.0 32bit and all of our applications from the documentation we wrote over a year ago from 4 months of testing and doing this exact procedure on our production box (K580). I used the exact same media, versions, patches, etc (unless they were specifically for the K580 model of course) and everything worked great except I couldn't add printers ... oh yea, JetAdmin software. I downloaded HP11d621.SD and installed the software. The printer installed just fine, but it won't print. The print job will go to the queue and disappears immediately (much faster than on other Unix systems ... too fast), but never prints. If I turn the power to the printer off, the job will actually sit in the queue. I did an lpshut and lpsched ... that didn't help. I can print to the printer via every other means (Windows & other Unix servers).

Any ideas? We didn't have this problem when we installed the production server. I've also got the replacement for JetAdmin downloaded ... HP11e118.SD, should I try to uninstall JetAdmin and install JetDirect Printer Installer? Any ideas would be greatly appreciated. Thanks.

... wondering why it wasn't in the documentation and why we didn't have problems with this on the production server ...

[steven Burgess_2]

Jason

Quite a fundamental question - Can you telnet to the jet direct card on the device from your server ?

Have you got the correct port configured ?

Steve

[MANOJ SRIVASTAVA]

Hi Jason


Jetadmin should work fine .

1.jetadmin should also give a menu to test the functionality of the printer possible print a test page. ( does it work ).

2. telnet tot he printer should be able to make you see the printer press neter to the passwd etc .I assume yoyu can ping to the printer.

3. Try deleteing all the rpinters created and just installing test printer to start with.


jetadmin make the lpscheduler go offlien so run lpsched . Also waht is the o/p of lpstat -t ? ps -aef | gerp lp should show something runiing too.


Manoj Srivastava




3.

[Jason Nickelson_1]

Thanks for the quick replies. I can ping and telnet to the printers IP address. The configuration looks to be ok. The JetDirect card doesn't have ports as it's an internal card compared to a multiport external print server.

From JetAdmin it does print the test page ... both the default test print file and a user specified text file. JetAdmin recognizes it as an HP LaserJet 4000 which is correct and it says access is allowed.

lpstat -t:
scheduler is running
system default destination: mislaser
device for mislaser: /dev/null
mislaser accepting requests since May 30 18:50
printer mislaser is idle. enabled since Jun 20 15:36
fence priority : 0

NOTE: Enabled since today because I disabled and re-enabled hoping to "kick-start" the printer. mislaser is the name of the printer in question and it is the only printer that has ever been configured on this server since I installed the server.

ps -aef | grep lp:
root 23266 20983 2 16:13:39 ttyp5 0:00 grep lp
lp 21057 1 0 14:28:03 ? 0:00 lpsched

After printing the test pages out successfully I tried printing from the command line again, using the same file I specified from within JetAdmin and it did not print (I also made sure the lpsched process was running before attempting to print from command line). I tried lp and lp -dmislaser ... no printouts.

[Dave Chamberlin]

Hi,
I would suggest you do a diff on that printers file in /etc/lp/interface using the file from your production server and the file on the test server. are they identical? Particularly, is the line with PRINTERCFG= the same in both? Also compare that printers file in /etc/lp/interface/model.orig - are they identical? I have had to fix some of my files to get them to print correctly.

[MANOJ SRIVASTAVA]

Do like this


cd /usr/spool/lp
lpshut
rm FIFO
rm SCH*
lpsched

this should work , or if nto then you will ahve to delete the printer and installa new one.

you can just use lp < filename > as the lpstat -t shows the printer as already default.

Manoj Srivastava

[Martin Johnson · Accepted solution]

Check file and directory permissions and ownership. Use a working system to determine the correct settings.


HTH
Marty

[Jason Nickelson_1]

Thanks to everyone for their suggestions. Sometimes it just takes a second set of "eyes". Turns out the /etc/lp/interface/model.orig directory had the wrong owner/permissions set. I set the correct permissions, deleted the printer, then reinstalled the printer and it works like a champ. Thanks again for all your help. :) Another happy camper.