Printer disabled

[so.nimda]

Hi,

There is a printer that keeps getting disabled. When I run the command "lpstat -pPRT6455" I get the the following error :

# lpstat -pPRT6455
printer PRT6455 disabled since Sep 7 09:31 -
error 1 returned
fence priority : 0

When I "enable PRT6455", the status returned is :

printer PRT6455 now sending PRT6455-0 to PRT6455. enabled since Sep 7 09:31
fence priority : 0

But after a while, the printer is disabled again.

I am not able to ping the printer as pinging has been disabled in the firewall/network. Traceroute is able to reach the printer.

It is a Canon IR 2270 without print server and there's no problem printing from the network, just that UX is not able to print to it.

Has anyone encountered similar issues?

Thanks

[TTr]

> It is a Canon IR 2270 without print server

What exactly do you mean here? There has to be a printserver involved. Is it internal in the printer? Or is the printer directly connected to a windows printserver?
How is the UNIX spool defined? Is it a remote spooler or a network spooler?

[Bill Hassell]

Has this printer ever worked from HP-UX in the past? There are two very different ways to connect a printer in HP-UX.

One is to use a remote lpr/lpd print server which is usually built into the LAN card in the printer. The other is to use HP's JetDirect software called hppi. However, hppi requires a LAN card that is compatible with the HP JetDirect protocol. You can check this compatibility by running the command:

/opt/hpnpl/bin/hpnpadmin -v 1.2.3.4

where 1.2.3.4 is the IP address of the printer. If it replies with a lot of data, then the printer can be added using addqueue. This is the preferred method to add the printer when hpnpadmin returns the printer details (more than a page of data and stats).

Otherwise, it must be added with SAM using the option: Add Remote Printer. You will have to use the correct lpd printer name. This is very difficult to locate in the Canon documents. The 2270 may have the lpd printer name "print", "PRINT", "pt1" or "lpt1".

[so.nimda]

Hi TTr & Bill,

Thanks for your reply.

After checking, I found that the printer is actually connected to a JetDirect print server via lpt1.

I have been searching through this forum and found that I need to install JetAdmin in my UX box to enable the printing.

Those threads that I read were actually dated 2002 / 2003 and not sure if the JetAdmin software is outdated. I managed to download "HP11e134.SD" but not sure if it will work with 11v2.3

Some queries :
1) how do I install it?
2) after installation, do I still use SAM to set it up?
3) if so, how do I specify that it's lpt1?
4) as there's no "/opt/hpnpl/bin/hpnpadmin" directory, does this mean I need to install "hppi" instead of JetAdmin (or are they the same)?

Sorry for all the stupid questions as I am at a loss as to how to get the printers working.

Thanks !

[Bill Hassell · Accepted solution]

Your questions are very normal. HP has always had a very big disconnect between their printer division (including the JetDirect products which include LAN cards and external boxes) and HP-UX. JetAdmin was the first product name but was obsoleted in 1999 due to Y2K issues, and was replaced by hppi (HP Printer Installer). The code is fairly similar but hppi is what you need. Unfortunately, HP stopped shipping hppi with the core HP-UX install disks years ago (for reasons unknown) and therefore makes installing HP printers quite problematic.

So your Canon will work just fine with hppi. Download the HP11e134.SD file (use BINARY mode if you transfer it from a PC to your HP-UX system. Store it in /tmp and install it like this:

swinstall -s /tmp/HP11e134.SD \*

Don't forget the \* at the end. Once installed, when you run sam, it will simply start hppi when you specify a "Network Printer". However, I find the menu quite difficult to navigate for a simple printer, so I use the hppi utility addqueue to add the printer.

Once your printer has an IP address, just add the printer like this (after you delete the old PRT6455 using: lpadmin -x PRT6455):

addqueue -h 1.2.3.4 -q PRT6455 -b off -e off -r off -i 261

The man page for all the available options is:

man net_ljx000

[so.nimda]

Hi Bill,

Thanks very much for your detailed explanation. It was most informative !

I will try it out and post any issues encountered.

Thanks very much !

[so.nimda]

Hi Bill,

Encountered error while trying to install HP11e134.SD :

======= 04/13/10 02:40:16 MESZ BEGIN swagentd (pid = 1899).

* Registered RPC protocol "ncacn_ip_tcp" with endpoint "2121".
* Registered RPC protocol "ncadg_ip_udp" with endpoint "2121".
* Checking job queue at 1 minute intervals.
* Started install agent on "/" for root@host, pid=26160,
09/13/10 02:33:52 MESZ
ERROR: Access denied to root@host to start agent on unregistered
depot "/tmp/HP11e134.SD". No (i)nsert permission on host.
09/13/10 02:33:53 MESZ
* Agent pid=26160 completed. 09/13/10 02:33:53 MESZ
* Started install agent on "/" for root@orion, pid=26216,
09/13/10 02:35:24 MESZ
ERROR: Access denied to root@host to start agent on unregistered
depot "/tmp/HP11e134.SD". No (i)nsert permission on host.
09/13/10 02:35:24 MESZ
* Agent pid=26216 completed. 09/13/10 02:35:25 MESZ

I have "chmod 777" but still no luck.

What should I do?

Thanks

[Dennis Handly]

>ERROR: Access denied to root@host to start agent on unregistered depot "/tmp/HP11e134.SD". No (i)nsert permission on host.
>I have "chmod 777" but still no luck.

You need to look at swacl(1M) for permission issues.

[Bill Hassell]

Try restarting swagentd

/sbin/init.d/swagentd stop
/sbin/init.d/swagentd start

Also, try the command:

swlist

It should report a list of software products that are installed. If you get errors, your networking setup on this system may have been recently changed, probably incorrectly.

The problem is not with the depot file but with the software installer programs.

[so.nimda]

Hi Dennis & Bill

Thanks for your replies.

Yes, restarting the swagent worked.

Continuing with the installation and configuration of the printer.

Hope it works...

Thanks once again for the prompt response. =)

[so.nimda]

Hi Bill,

Software installed successfully.

When I tried running "addqueue -h 1.2.3.4 -q PRT6455 -b off -e off -r off", there's an error :

sh: addqueue: not found.

I checked and found that it's in "/opt/hpnpl/bin" :

-rwx------ 1 root bin 36864 May 28 2002 addqueue

Seems like the installation is "not complete" eventhough there was no error as I am not able to do "man addqueue" - error "No manual entry for addqueue."

Also what is the switch "-i 261"?

Sorry.. I am very bad at this... =(

Thanks for your patience.

[so.nimda]

Hi Bill,

Pls disreqard my last post.

Been looking up past ITRC posts and found nuggets of helpful info.

Managed to get the queue created. I have sent a printout there and awaiting confirmation that it's printed (the printer is at a far away location).

Thanks very much for you patience and help.

Really appreciate it.

Regards

[so.nimda]

Hi Bill,

Seems like it's not working. While I had no problem installing hppi and adding the queue, it doesn't seem to be printing.

I tried sending a text file for printing :

# lp -dPRT6450 test
request id is PRT6450-4 (1 file)

and when I check it using "lpstat" it's always showing:

# lpstat -pPRT6450
printer PRT6450 now printing PRT6450-4. enabled since Sep 13 09:00
fence priority : 0

Did I miss anything?

Thanks & regards

[Bill Hassell]

Run the command:

hpnpadmin -v 1.2.3.4

where 1.2.3.4 is the IP address of the printer. It should report a long list of information and statistics. If you get an error that the printer is unreachable or not responding, you may have port 9100 disabled in your firewall. You'll need that port open.

[Bill Hassell]

Sorry, I missed the previous questions...

> When I tried running "addqueue -h 1.2.3.4 -q PRT6455 -b off -e off -r off", there's an error :
>
> sh: addqueue: not found.

The path for /opt/hpnpl/bin was added to the HP-UX login PATH but you must login again to get it updated. The path is stored in /etc/PATH.

> Seems like the installation is "not complete" eventhough there was no error as I am not able to do "man addqueue" - error "No manual entry for addqueue."

Actually, this is the same problem as above. Your $MANPATH variable must be updated by logging in again.
>
> Also what is the switch "-i 261"?

This is the printer ID. The addqueue program automatically identifies HP printers but nothing else. The printer ID 261 is the closest HP printer ID and simply selects the printer model script for your printer.

Were you able to add the printer using addqueue? If you used SAM, you must select the "Network Printer" option (which runs hppi). If you used "Remote Printer", you set it up the same way as before.

[so.nimda]

Hi Bill,

Thanks for taking the time to reply.

With your help (many many thanks !!), I managed to get those printers with JetDirect connection printing. =)

But I also have other Canon printers that are connected via "built-in" network cards (not JetDirect print server).

Using the "addqueue" for these printers doesn't seem (although they worked for JetDirect connected ones) to work as the spool seems stuck.

I have also tried using "SAM -> Adding Remote Printers" but that didn't seem to work either.

I sent a simple text file to the printer and here's the result of "lpstat -o" & "lpstat -p" :

------------------------------------------
# lp -dPRT2230 README-HP.txt
request id is PRT2230-1 (1 file)

# lpstat -oPRT2230
printer queue for PRT2230
-- Idle
PRT2230-7393 root priority ? from
PRT2230-1

host1: PRT2230: ready and waiting
no entries

# lpstat -pPRT2230
printer PRT2230 is idle. enabled since Sep 14 13:42
fence priority : 0
------------------------------------------

"lpstat -o" & "lpstat -p" seem to show stuck spool?

Thanks once again for your help & patience.

Regards

[Bill Hassell]

> But I also have other Canon printers that are connected via "built-in" network cards (not JetDirect print server).

As I mentioned above, there are VERY few non-HP printers that are compatible with HP's JetDirect protocol. The Canon ImageRunner series (big and expensive) may have JetDirect or port 9100 capability) but smaller one do not. These printers can only be connected using the "remote printer" method in SAM (or lpadmin).

> Using the "addqueue" for these printers doesn't seem (although they worked for JetDirect connected ones) to work as the spool seems stuck.

addqueue is only for JetDirect printers. Using will setup the printer for HP protocol, so your Canon printers just ignore the attempts to print.

Use removequeue to remove PRT2230 (since it was added with addqueue). For all other printers, you would use lpadmin -x to remove the printer.

Now before you add the printer using SAM, you need to find out what internal name is required to use the printer. The remote printer protocol is called RFC 1179 and is primitive by today's standards, but all SysV Unix systems (like HP-UX) must use this protocol.

After deleting the printer, run sam and select printers, and Add Remote Printer (not Network printer). There will be 3 lines to fill out:

Printer name (the Unix print queue name)
Remote System Name (the printer's IP address)
Remote Printer name (the internal name of the printer)

The 3rd line is the most difficult. I've tried to keep a running list of the dozens of printer manufacturers with their internal names. For Canon, the names are print PRINT XJDIRECT pt1 or lpt1. The best answer would come from the manufacturer but when you mention Unix hosts, support folks get very nervous. If you can't get the name(s) for your printers, you'll have to try each one. Add the printer and send a job. If it hangs, delete the printer and try another name.

[so.nimda]

Hi Bill,

Thanks a lot for your patience and replies !

I have really learnt a lot about unix printing from your detailed explanation.

Just so you know, I have managed to get those Canon printers printing, all thanks to you !

Thank you once again for your patience and help !

Regards

[so.nimda]

Issue resolved