Jump to content

Ricoh printer driver configuration tool: Printer Driver Packager NX


Recommended Posts

Posted (edited)

I've deployed pin protection using the modified driver for Ricoh Aficio mp500b (quite an old model).

 

Think my case is slightly different to yours (I was looking to prevent people printing / copying when not authorised to use that specific printer, and logging who is printing and copying how much - but when a job is submitted with a valid pin it just prints like normal. I would think secure print is holding the job on the printer until the user is physically there to release it)

 

Although I've got it working it did take quite a bit of fiddling and experimenting to get to that stage. It was a number of years ago so cant remember the exact process of sorting the driver, but it sounds like you have done that so a couple of things to note when configuring the printer on your computers:

 

>I've found windows likes to pick the driver it thinks is right, sometimes even if you tell it the modified one. Be sure it is manually specified to use the modified version either when installing the printer or in the printer properties/advanced screen - and double check it has stuck with the one you chose too - ive had a couple of computers revert to the generic one after installation.

>In my use case, if it rejects a pin, it wouldn't show anything on the computer, the printer would just discard the job without printing and log it as an authentication error in its own logs - so do check the printers logs if you think the computer is set up correctly and the computer says the job is printed - when the printer was discarding my jobs the computer thought it has printed successfully & it was the printer logs that highlighted the pin code not being recognised.

 

>You mentioned an MSI file - i cant remember the options it gave but the files i use to configure new computers with this printer are just the unpacked driver file, and then the devices and printers properties in windows to select the modified driver. if you see that as an option or can extract the driver files then perhaps try that?

I know you may have already realised those points but i know how it can be when you have been working on something that just isn't going to plan and how easy it can be to overlook the simple points so just wanted to mention the two things that finally helped me "crack" the problem in case it helps you too

Edited by lreid
reread the post, added ref to msi files

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...