For testing purposes, I've got the machines connecting to the printer two different ways.
1. Through the LAN via a Standard TCP/IP port
2. Via the print server through an Internet port
When I print through connection #1, it sends the print job, including the name of the job, the computer it's coming from, the document size, and then once the job is loaded, it loads the page count last.
I'm wondering if there's some sort of communication between the computer and the printer. If that's the case, it appears this pingback communication is not happening when the job gets loaded into the print queue.
Then again, it might be my setup.
Generally, how print jobs are handled are that patrons send print jobs to one printer setup for my HP 5200 printer. This printer setup is constantly on pause. When a job comes through to be released, it's moved to a different setup for the HP 5200 that's unpaused, and the job prints.
I tried to find some sort of setup in CUPS that forced all jobs to come through "on hold", so that all I had to do was simply release them, but I couldn't find anything in CUPS, nor in any documentation I searched.
So I wonder if it's not communicating with the printer because I've got the printer queue "paused". After I move the job, and after it prints, it will show the page count. However, when I pause the printer in Windows, it'll still show page count. Go fig.
What I need to figure out is how the computer is communicating with the printer.
Otherwise, we may simply have to cope. But anything I can do to make their job easier is pretty much what my job is all about.