setting up non-hp network printer

[Dave Chamberlin]

I am trying to set up a canon network printer on my k box (10.20). I can ping the printer from the command line so I know it is alive. When running jetadmin I cannot configure it. I try the diagnostic to test the printer's accessability - it gives:
Receive - no snmp response ...
either incorrect GET community name, not an HP network printer...etc

What does this mean? Can I not send jobs to this printer?

[Eddie Warren]

Hi Dave,
Try "SAM" and configure it under Printers/plotters by "add Remote Printer/Plotter". If you are just adding it to your K-box this should work for you. You
will not be able to configure it with Jet Admin. Hope this helps.
Eddie

[Rick Garland]

You shoud be able to use the jetadmin as well as use SAM.

I believe that jetadmin only needs reponse back from ping to proceed with printer setup. It will still tell you that it is a non-hp printer and provide a list of drivers that can be used.

When doing the configuration, use the dumbplot driver as a start. You can try other driver files until you find the one that suits your needs.

And don't forget, SAM is there as well!

[Rita C Workman]

For non-HP printers with non-HPJetDirect cards, I believe you need to set these up as remote printers via SAM.
JetAdmin is an HP tool for setting up HP network enabled printers via the JetDirect cards. That is why you are getting the snmp errors.
But since you can ping the device....you should be able to set it up via remote printing or if you have something like Openspool you can add it there.
Regards,

[Richard Mertz]

If the printer has a parallel port, you could use a JetDirect box. We use these for our Toshiba network printer/copier machines that only came with windows drivers and a somewhat proprietary set of commands. I modified a printer model to match the command set for the Toshiba and they work pretty well.

[Dave Chamberlin]

Let me clarify. I am trying to print to some new copier/printer/fax machines as network printers. HP calls these "remote" printers, though they are network devices (not connected to a computer). I have set them up as remote printers now and 2 of 6 can be printed to. The others all indicate "waiting for ... to come up", even though they can be printed to from PC's. I was told that the remote printer name must be a specific (fiery) name in HPUX for these to work. Has anyone heard of this? Where does HPUX specify a remote name for a printer?

[Victor BERRIDGE]

Hi Dave,
When I used to get this messages, i rarely found the trouble HP-UX side, once you have given a name and IP addr. in /etc/hosts, then using sam =>printers and plotters=> add Remote Printer/plotter, I put printer is on a BSD System and allow Anyone to Cancel a Request.
When this message appears, I usually remove the printer and add the printer again, THEN I can blame whose responsible=> Novell...
Because it happens mostly with queues shared with other systems who are in fact the real print servers. Remove a faulty printer from your sytem, reinitialize you printer and declare it again
Greetings
Victor