Here's the situation:
I have two HP 4350dtn Printers w/ 96MB RAM directly connected to our network using their built-in Jet Direct Card.
I thought it would be fairly simple to enable pooling between these two but alas nothing's ever easy.
Both printers were individually installed as network printers to a (Jet Direct) tcp/ip port on our server.
Then I renamed one to include -pool in the name. Shared it, enabled pooling and checked the additional tcp/ip port I wanted associated with the other 4350. When I sent two 20page PDF print jobs I expected one to go to each.
Well they both spooled to the same printer one after the other as would happen if there were only one.
I then removed the printers and ports from the server and tried again. The second time I installed the printers as "local" but pointing them to the recreated tci/ip ports. Same results.
Additionally I turned one of the printer off to see if that would cause a job to go to the other printer. Nope! It just sat in the queue indicating the port of the printer that was off. The printer never even reflected that it was offline.
Here are my questions:
1) What am I missing with regard to setting up a printer pool?
2) What signals the server that a printer is busy? (Does all 96MB of memory need to be full with more waiting to spool?!? I think it should be considered busy if it is printing anything.)
Thanks to all for any leads.