Jet Direct Printing Problem

[Tom Horan]

Here should be an easy 10 points !

We have move a Jet Direct box connected to a line printer from one network to another, changed the config of the jet direct box to the new network and modified its settings in Jedadmin and the hosts file on our UNIX box.

We can telnet onto the Jet Direct box fine, we can also print a test page from the jetadmin box to the printer but we can't send anything from the UNIX side to the printer, it just sits there in a queue.

Any ideas ?

[Mark Greene_1]

A few ideas, in no particular order:

- Check /etc/nsswitch.conf to verify the name resolution order. If you are using DNS or NIS and still have an entry there for the old address and the host file is not being checked first, that would be a problem.

- Did you restart lpsched on the hp box after making the changes?

- Did you inadvertantly change the default queue name on the jet direct box?

- Are you seeing any messages in /var/adm/syslog/syslog.log or in /var/adm/lp/log that may be related, or timestamped around when you are sending the test prints from the unix box?

- what does rlpsta -d[printer] return?

- what does lpstat -t return?

- is snmpd running?

HTH
mark

[Bill Hassell]

(all this assumes you are using HP's JetAdmin or Printer Installer software)

When you added the printer originally, you had the option to specify to the printer's hostname or IP address. This is hardcoded into the primary lp script for this printer in /etc/lp/interface. If you used the printer's name, then the command:

nslookup printer-hostname

will tell whether your computer knows the IP address now that it has been changed (this is typically a DNS or /etc/hosts issue). If you used the IP address, dso this:

disable printer-queuename

edit /etc/lp/interface/printer-queuename
change PERIPH= to the correct IP address.

enable printer-queuename

You can verify that HP-UX can talk to the printer with:

/opt/hpnp/bin/hpnpadamin -v printer-hostname

(if you have Printer Installer, it will be /opt/hpnpl/bin).

Or you can save yourself a whole lot of time and in 5 seconds, type the commands:

removequeue -f -q printer-queuename
addqueue -h new-IP-address -q printer-queuename

[Tom Horan]

Bill

I took up you suggestion and romved the printer (removequeue), but when I tried to add it, it could not contact the box.
I added it from Jetadmin and that worked fine but the only problem is that I don't get any option for the Jet Direct box in Jetadmin so I used a dumb plotter.

Still my docs sit in the queue waiting. Any more ideas ?

Mark

The System name on the Jetadmin box is exactly the same as on the UNIX side of things. Nothing in the los either. lpstat returns the jobs I have sent to the printer, lpstat -t shows all my other printers and the problematic one accepting connections.
all the ohter printers are working fine, so I guess it is a problem with the config of the printer/jetdirect box.

Any more suggestions lads ?

[Mark Greene_1]

can you traceroute to the jetdirect box?

mark