Canon Photocopier - Network Printing

[Iain.Faulkner]

Afternoon All,

 

Slightly strange one this.

 

We've recently invested in a number of Canon Photocopiers for around school, which have all been networked and installed on our Print Server (running Server 2008).

 

The photocopiers have installed fine, and you can send a test print to them from the server, which again prints fine and as a result I rolled out the photocopier via group policy to those users who required access to it.

 

However, when they try and print to the photocopier, they are prompted for an account code (as we expect) which they enter, but once they press enter to send the document through to print they see the following message "Could not get device information" and as a result they cannot print.

 

I have now set the photocopier in question (an IRC3080I) up as a lcoal printer through a standard TCP/IP port and this allows the users to print successfully, but obviously it means we cannot track how many copies are being done and by which account, which we'd like to be able to do.

 

Has anyone else had similar issues?

[kearton]

I'm having the same problem with a new iRC5045i. However the Mono iR7095 copier works fine.

[skell]

We had a similar problem. We ended up using the UFR II driver for the photocopiers.

 

Here is a generic link. Canon U.S.A: Support

 

OP didn't say what model, but the UFR II driver I believe supports most if not all of the Canon photocopiers.

 

EDIT: Sorry, you did! Here is the link http://www.usa.canon.com/opd/controller?act=OPDSoftwareAct&fcategoryid=2172&modelid=16849

 

And for the C5045i http://www.usa.canon.com/opd/controller?act=OPDSoftwareAct&fcategoryid=2172&modelid=19465

 

I also had to install the NetSpot device installer I think on the print server. Link http://www.usa.canon.com/opd/controller?act=OPDSoftwareAct&fcategoryid=2291&modelid=3638

Edited June 16, 2010 by skell

[kearton]

If I print directly from the server (2003, not 2008) it works fine. If I print from a workstation to the shared printer it errors. The Server is running a "Canon Driver Information Assist Service" and I think it's this which lets it work. I really don't want to have to install this on all the workstations...

[skell]

You don't have to install it on all the workstations. Are you using the UFR II driver?

[kearton]

no, PCL5c

[skell]

Install the UFR II driver on the server, and the XP driver on the server as well. Re-deploy the printer via AD and it should work.

 

EDIT: Actually, you don't need to redeploy the printer. Just change the driver its using on the server to UFR II. If you have installed the XP driver it should just switch over.

Edited June 16, 2010 by skell

[kearton]

If an ID and PIN work directly at the copier to do photocopying, should the same combination work when printing to the copier?

Because I've changed to the UFR II drive, but I'm now getting a different error when I use a known good ID and PIN:

Could not verify the Department ID and PIN specified in Department ID Management

 

EDIT: That's from an XP workstation. When I try the same ID/PIN from the 2003 Server I get:

Incorrect Department ID and/or PIN. Specify the correct Department ID and PIN

 

I'm going right off Canon...

Edited June 16, 2010 by kearton

[skell]

Yes the same combination should work. When you click on "Get Device Information" from one of your workstations and do you get the message "Got Device Information"?

 

EDIT: Sorry, that setting is under the Device Settings tab. Also make sure you tick "Job Accounting". You can verify that the ID and PIN are working under "Settings" next to Job Accounting.

[kearton]

No

 

Warning

Could not get device information

[skell]

What about on the server?

[kearton]

Yes it works on the server.

 

Information

Got device information

[skell]

Check what print driver the workstation is using. I suspect it may need changing if you didn't reboot.

[kearton]

Workstation says it's using the UFR II driver...

[skell]

Untick "Enable advanced printing features" in the Advanced tab on the workstation and check again

[kearton]

no joy

[skell]

Did you run the setup for the UFR driver or manually install it?

[kearton]

I went into the printer properties on the server and changed the driver, then added the printer on the workstation. I didn't run any setup.

[skell]

I think I remember using the installer for the UFR driver when I installed it on the server. Try that.

 

Quite frankly I'm out of ideas now sorry!

[kearton]

ok I'll give that a go. Thanks for your help!

[mac_shinobi]

What are the client operating systems ? XP from what I can gather from above posts ?

 

Just wondering if you re add or change the printer ports on both the server and on the clients to use LPR and enable the LPR ( LPR Unix print service ) on windows xp and re add again, obviously you will need a que name which I am guessing may be PRINT in uppercase but will have to check canon documentation ref que names and see if that helps at all ?

 

shot in the dark though

 

Also I know SBS had an issue with SNMP being enabled and it then showed the printer as being offline so just curious if you disable SNMP on the port configuration on the server and client and see if that helps ( long shot again ) probably most likely not related.

[diagram]

I had a similar problem, in the end I just lived with it and put the UFR II driver on workstations and printed to an IP Port.

The copier account print-outs add one count each for A4 and A3 so you need other softwares to do the accounting properly.

[mullet_man]

as long as you install the

 

Canon Driver Information Assist Service

 

it should be good, double check the Canon service is running on the server.

[actech]

I get that problem from time to time with our ir5020. Just reinstall the Driver information Assist Service (DIASsetup.exe) on the server and it should come back fine.

[Barticus]

Did you have any luck in resolving this problem? We are deploying a Canon I/R C5030 and have run into the same issue that you have and I am about ready to give up on Department IDs altogether.