Scheduler keeps disabling printer (10.20)

[Erwin Mascardo]

A user I'm supporting has a 715 workstation with a LaserJet 4100 locally attached. Every time a print request is sent (with the scheduler running and the printer enabled), the request gets queued up, but nothing is produced.

lpstat -p shows that the printer has become disabled, with the following error: "can't open /dev/c1t0d0_lp".

I've scoured previous forum posts on this (and similar) problems, and I've done the following, all with no result. In no particular order...

1) I've stopped the scheduler and cleared /var/spool/lp/outputq (FIFO and SCHEDLOCK were removed properly by lpshut). Then I manually enabled the printer and restarted the scheduler. Nothing.

2) The control and data files appear properly in /var/spool/lp/request/. Like I said, the jobs queue up properly.

3) I've tried several interface scripts, though I think some of them are for networked printers only. What should I be using? (Although the next point seems to discount a problem with the interface scripts.)

4) Here's the telling clue, though I'm not sure what to do with it. If I try to send a file directly to the device file (cat /etc/copyright > /dev/c1t0d0_lp), I get the following error: "sh: /dev/c1t0d0_lp: Cannot create the specified file." I've checked permissions (666) and ownership (lp:bin). I even recreated the device file from scratch, just to make sure the major and minor numbers were right. CentIf is loaded into the kernel, and ioscan shows that the device is claimed.

The fact that I can't even drop a file onto the device file directly is what bothers me. Is this a software problem, or is it something stupid like a faulty parallel cable (or port)?

One last problem: I'm on the East Coast, and this user is in California. So I can't jiggle the cables myself or look at the printer's front panel (I don't even know what a 4100 looks like, much less what's available from the menus). If anyone suggests checking or changing settings from the front panel, please tell me which buttons to press (and how many times), so I can tell my user...thanks.

[harry d brown jr]

Erwin,

Try this thread:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xc8bb119c3420d411b66300108302854d,00.html


live free or die
harry

[MANOJ SRIVASTAVA]

Hi Erwin

It looks either the Printer is not online or the cable is loose as a raw dump on the parallel port should come out with a proper status . In any case can u try to switch off the pritner adn the machine and then switch on in the same sequence .

Also you can try reinstalling the printer using a differnt name just to try it .


Manoj Srivastava

[Erwin Mascardo]

Okay, thanks for your help (Harry, that thread was one of the procedures I already tried). However, I just got a call from my user...seems that the thing is *not* connected locally, but is networked! So of course I can't dump directly to the parallel port, and of course it won't respond to anything I try regarding the parallel port...

Isn't it great when people tell you stuff like this after you've beaten your head against the problem for a few hours?

[pap]

Hi Try installing this patch.

PHCO_25109

It might fix your problem.

Thanks,
-pap

[MANOJ SRIVASTAVA]

Hi Erwin


That was the first thing I was trying to think and reply that whether yuo can use jetadmin but then once i read you question more carefully I realised it must be connected to parallel port. One thing you can do is to telnet to the printer port and jsut get the status.

Also I beleive you are good at jetadmin

All the best.

Manoj Srivastava

[Erwin Mascardo]

Thanks for all the time and help, everyone. Points may look a little thin, but that's because my problem turned out to be not at all what I originally thought it was...

JetAdmin wasn't recognizing the printer, so I upgraded to the latest version of JetDirect. I also had to apply PHCO_22268 so that SAM would realize that I was using JetDirect and not JetAdmin. Once both of these were done, the workstation talked to the printer just fine.