Ok we're all friends here, lets keep this civil for the new guy.
First off.. ssampier, why are you complaining about OES2 when you're still in the stone age on NetWare 6? OES2 is irrelevant to your current problem. Another thing, iPrint is NOT a management tool, so your comparison is a little off. Now that I got that off my chest, lets get this problem solved. Since you are new, you need to understand some fundamentals.
First of all, ConsoleOne never has and never will be able to manage printers. For printers, you use either NWADMIN or iManager. However, iManager SUCKS on NetWare 6.0 and it's kinda like trying to use Chopsticks to eat soup. Plus it sounds like you are using only NDPS, not iPrint (this is based on info you provided). With that, NWADMIN is probably all you need.
Let me get on my soapbox for a sec.. A lot of people get butthurt about the different management tools that Novell has. But they don't understand the history. NWADMIN is a legacy tool for a Legacy OS. NetWare 6 is Legacy. You can use NWADMIN to manage printers, but it does not have the full functionality of iManager. There are SEVERE limitations in NWADMIN that you have to just accept if you continue to use it (like XP support), but you can get printers to work with basic functionality. Also, your iManager is probably version 2.02, which does not have the same functionality as does iManager 2.5/2.6/2.7 that you find in later versions of NetWare and now OES2. (Note that NetWare 6.0 is essentially 4 generations back - NW 6.0, NW6.5, OES1, OES2). Although there are a few reasons why I still use NWADMIN for some things, I don't use it for printing, and only use it when its easier than iManager. ConsoleOne is another story, but not relevant here.
So I would recommend using NWADMIN only because you ARE using NDPS and NetWare 6 and it will just be easier to go along with what you've already got.
There are a couple things here that need to be explained.
1) When you delete an NDPS printer in NWADMIN, it does not delete the agent from the NDPS manager. So you probably didn't actually recreate the printer, you probably created another one. You need to go to the NDPS Manager on the server and review the list there, look at the status, etc. If you need to remove a printer, remove it from the server screen and it will also delete the NDS object from the tree. Then you can start with a clean printer agent.
2) HP NDPS gateway sucks. It crashes a lot, is very unstable, and this is a real dilemma cause I LOVED the HP gateway back in the day for it's functionality. But the reality is that you can't use it anymore if you want a stable server. You NEED to convert ALL your printer agents to the Novell NDPS Gateway (Or referred to as the Novell SNMP gateway). This is a 20 second process if you download and use the Novell Conversion tool found here: http://support.novell.com/docs/Readmes/InfoDocument/patchbuilder/readme_5006642.html
. Make sure you unload the NDPS manager and reload the NDPS manager after you do the conversion. I've never had a problem with it, and you can run it multiple times if you don't think you got it right. If you do it right, after you reload the NDPS manager, you wont' see the HP Gateway Agent screen anymore.
3) Note that Novell tends to use NDPS and iPrint as if they are the same thing. They are not. They both use the same NDPS agent backend, but the iPrint adds some additional modules, and the both have different delivery mechanisms to the client. NDPS delivery integrates with the Novell client; iPrint delivery has its own separate agent. iPrint is the only supported printing platform on OES2.
4) When your server is not talking to your printer, but you know the printer is active and working, you need to troubleshoot the configuration. Maybe it can't ping the printer, maybe it can ping but it can't talk to the printer. If you continue to use the HP Gateway, you should be able to look at the printer list and see the status of communication (That's what I like about the HP Gateway) I recall a <===> if it's talking, or < /\ > (??)if it's not.
5)You can also look at system logs to see if any errors occurred while loading the NDPS agent. Each printer that loads will invoke an automatic load from the console. So you need to check SYS:SYSTEM\SYS$LOG.ERR for any printer related errors.
6)Also, for the record, a lot of people go down the route of "Just go Direct IP, It's easier".. Well, for 1 or 2 systems, yes, much easier. For 30 or 500, hell no. You will spend the rest of your life managing printers. Get this problem solved on the Novell box and kill the direct IP printing.
If you see any errors or status messages, you can also search the Novell knowledge base at support.novell.com. It's actually very good.
Or you can report the errors back here and maybe we'll be able to better point you in the right direction. Also, stop deleting printers, this isn't Microsoft and you shouldn't have to do that to fix things.
7)Also you should go to HP website and download the HP Download Manager. Search for it in drivers downloads. You can use it to find your printers and update your firmware. This will help ensure that your printers have the latest code and work correctly with NDPS.
8)Make sure on your printer, LPR is enabled if the option exists (usually does).
9) Remember that just cause you can ping printer from workstation, doesn't mean you can from the server. Get on the server console and do some pings from there.
10) And if you're angry at some of the things I said, lighten up cause I'm just messing with you.
PS - Lawnboy, While I share your enthusiasm for NWADMIN, I have learned that iManager gives you far superior Windows XP printer management, and now with iPrint Client Management, you can deploy your printers automatically by container or group just like you can with NDPS and NWADMIN. And using IPRINT, you get away from those nasty Windows Driver Warnings that are terrible with NDPS.
Marvin Huffaker, MCNE
Marvin Huffaker Consulting, Inc.
A Novell Platinum Partner