printer prints from one server - not another

[Dave Chamberlin]

I have a printer configured as an LJ4 on two servers, one running HPUX 11.0 (A), the other running HPUX 11.11 (B). Jobs print fine from server A (also configured as LJ4), but hang in the queue on server B. I tried copying the files from /etc/lp/interface for that printer from A to B (to see if a difference in the script file or model.orig file could be the problem), but still the queue hangs. I tried recreating the queue from scratch - same results. The printer is a multifunction Ricoh Aficio MP2510. It points to a problem on the B server, except I have hundreds of other printers on this server that all work without problems, including other multifunctions. Any ideas?

[OldSchool]

I'm assuming that you've configured it as a network printer, so

can you ping the printer by IP from both hosts? or by name?

does the work from B and then hand or does it always hang?

[OldSchool]

I'm assuming that you've configured it as a network printer, so

can you ping the printer by IP from both hosts? or by name?

does the work from B and then hang or does it always hang?

[Rita C Workman]

I tend to go to the obvious first.

Is printer enabled ?
Could it be a network issue? - Can you ping printer LJ4 from server B ?

Just to get you started,
Rgrds,
Rita

[Dave Chamberlin]

The printer is pingable by name/ip from either server. I tried disable/enable for the queue as well as lpshut/lpsched - as sometimes this had cleared past printer issues. Under SAM, the printer status is "busy" on the problem server, and "idle" from server A. BTW- I have one other multifunction at the same remote site that exhibits this behavior. In my experience, the "busy" has almost always resolved to something on the printer end.

[A. Clay Stephenson]

The very first thing to establish is if this thing is a Network (in HP-UX speak) printer or a Remote (in HP-UX speak) printer. Network work printers use the HP JetDirect (Ports 9100-910x) protocol and Remote printers use the LPR/LPD (port 515) protocol. If your Ricoh Printer supports the port 9100 protocol then add it as a Network printer otherweise you must add it as a Remote printer using hppi or the addqueue command. If it's a Remote printer, then often the remote printer names (e.g. TEXT, RAW, ...) matter.

[Dave Chamberlin]

We have it configured as a network printer on both servers (though it does not actually have a jetdirect card).

[skt_skt]

How does the below command responds?

"telnet n/w-IP 9100"

is that responding to hpnpadmin-?

hpnpadmin -v n/w-IP.

Could you describe a little abou the way you add the n/w printer.

[Dave Chamberlin]

Interesting - from host A I can establish the telnet session - but host B indicates "trying..." and does not connect. A traceroute shows the same hops from both servers.
The hpnpadmin -v command returns "receive no snmp response" from both servers. This is the same response I get from all our multifunction printers though...
I use SAM to configure the printers.

[skt_skt]

there is some reestctions....

you said there are other n/w printers wokring fine frm the server B. Are these working printer and not-working one under the same subnet.?are the host A and B on same subnet.?

[Dave Chamberlin]

The hosts are both in the same subnet. The printers at that remote site are on a different vlan, though some printers at that site are responsive and some are not. The ones that are working allow the telnet connection to 9100.

[skt_skt]

what i would do in this kind of situation is try to simulate the probllem on my test work station...

[A. Clay Stephenson]

If the printers will respond to some hosts and not to others, I would look for an off by one bit subnet mask.

[Dave Chamberlin]

At the moment they replaced the printer with the previous printer (an HP 4350) and it works without any problem. I still have 2 other multifunction printers at this location that have the same behavior though...

[skt_skt]

it looks like this model does not support UNIX prinitning.. try configuring the printer on windows box and configure it as remote on the UNIX side..

[A. Clay Stephenson]

It appears that your 2510 does support the port 9100 protocol. I noticed in the manual that the default timeout is 300 seconds. This means that unless specific commands are sent that no output may appear for 5 minutes. If some 2510's are working with respect to HP-UX and others are not then I would first make sure that all MP 2510's are running the same version of firmware.