I have a printer running on an external JetDirect 500x box hooked to a HP 4200 printer (3 trays). I have a queue setup on a Netware 5 server and then attached that queue to the JetDirect box. Here's the problem:
The printer is in an open area and for some reason sensitive data is being printed to the printer where:
A. it has no business going
B. is printed when no one is at the station near the printer
These reports print out of a specific system, so I had the analyst responsible for that system check who printed the reports. That analyst flagged a specific user as printing the reports. I spoke to and remote controlled the computer of the suspect user, but there is no way that user printed to this printer, because it isn't even installed on their system and they do not have rights to install a printer. The analyst claims the only way those types of reports are printed is from printing from that specific program directly to a locally installed printer on a computer.
We installed PCOUNTER a few months ago to audit and clean up old Netware print queues and it is now past it's shareware trial period, so I cannot use that. There's also a vendor machine that is using the queue (surprisingly, it's made by the same company of the program, but the analyst claims there is no way the report is coming from the vendor machine), so I cannot simply rename the queue to something else. And, do to the current constraints of another printing system, the queue must be left on the Netware server.
Now, I can connect to the Netware queue from my Windows 2000 box and watch print jobs come and go, but obviously I cannot do this all day. I'm thinking if these reports print on a certain night I can have them turn off the printer when they leave for the day which will freeze all print jobs in the print queue until the next morning until they turn the printer on. Then I could look at the print jobs and then have them fire the printer up to see if any of the "bad reports" come out. What would be nice is to have a Windows 2000 utility to monitor a Netware queue. And have this utility be free. :o)
We do have a Windows 2003 print server cluster and do plan to move from Netware slowly, but reports for another system come through our Netware SAA gateway and we haven't completely setup our Microsoft HIS gateway to replace the Netware SAA gateway, so for now this printer MUST use Netware! We don't want to spend several hundred dollars for PCOUNTER just for this one case of auditting.