12180 Views 9 Replies Latest reply: Oct 2, 2008 10:04 AM by Tim Blevins
First of all, if the job appears to leave the Mac but not print, I would check the logs on the printer. If there is some type of controlled printer usage (our Canon's have a similar thing called Job Accounting) then the job would show in the log but have some sort of error code to indicate it was not printed using a valid account. If this is the case, then I would expect there to be a sub-menu within the driver to input a valid account ID. With our Canon driver, there is an item called Special Features and within that menu is Job Accounting, which is where the ID and password can be entered.
If the printer log doesn't show your print job being blocked, then it may be a problem with the queue name. For a number of printers, when you connect to the printer via LPR, you have to enter a valid queue name. Without the correct queue name, the print job can leave the Mac but never find the correct port on the printer. If you are unsure what queue name is required, you could create the printer queue again but this time using HP JetDirect Socket (aka Port 9100) as the protocol.
Since there doesn't appear to be a record of the job leaving the Mac, then it would be good to see the cups error log on the Mac. Navigate to Applications > Utilities and open Console. Click the icon to show all the logs and then in the list, expand /var/logs and then expand cups. Here you will see the error_log. Every time you print a record of that print job is kept here. If you could try printing again to the KM and then copy these recent entries in the log back here, we may be able to see what is going wrong.
Also, how is the printer connected to this wireless network? Is it connected via Ethernet to the wireless router?
And can you explain how you connected to this printer from the Mac, ie which protocol you used, what queue name you entered, etc.
Sorry about the delay in replying. Not been to work for a while.
The error log is as follows:
I [18/Jun/2008:14:51:30 +0100] Adding start banner page "none" to job 334.
I [18/Jun/2008:14:51:30 +0100] Adding end banner page "none" to job 334.
I [18/Jun/2008:14:51:30 +0100] Job 334 queued on 'KONICAMINOLTA_bizhub_C252_52_C0_4D' by 'andrewrennie'.
I [18/Jun/2008:14:51:30 +0100] Started filter /usr/libexec/cups/filter/cgpdftops (PID 310) for job 334.
I [18/Jun/2008:14:51:30 +0100] Started filter /usr/libexec/cups/filter/pstops (PID 311) for job 334.
I [18/Jun/2008:14:51:30 +0100] Started filter /Library/Printers/KONICAMINOLTA/filter/pstokmc252 (PID 312) for job 334.
I [18/Jun/2008:14:51:30 +0100] Started backend /usr/libexec/cups/backend/mdns (PID 313) for job 334.
The printer is connected to the network by RJ45 from, presumably, the ethernet card to the wifi router.
I'm not sure about the last part of your reply. When I added the printer using the Printer Setup Utility, I added it using the Default Browser option to add a printer as opposed to using the IP Printer.
Thanks for all your time and effort - it is much appreciated.
The last entry indicates that a multicasting protocol like Bonjour is being used. This fits your description of how you added the printer via the Default browser view. Since this connection method is not working I would try adding the printer again but using IP > HP Jet Direct. This will require you to enter the ip address of the printer and then browse for the printer model. If you cannot find the C252 in the list then the Generic Postscript will at least let you test the connection.
One note. The HP JetDirect connection is aka Port 9100. If there are Windows users on your network they generally default to this protocol when they add the printer. However sometimes this port may not be enabled or even available on the printer so you may need to print a network configuration page from the KM to see what is enabled. Or you could check one of the PC's port configurations to see their setup. In short, the answer is to do what they are doing.
So I have finally gotten round to trying to get the printer set up using the IP address. I found the Configuration Page on the printer and have all the settings however when I added it as a new printer it still didn't work.
I copied the error log:
I [14/Aug/2008:15:01:03 +0100] Adding start banner page "none" to job 386.
I [14/Aug/2008:15:01:03 +0100] Adding end banner page "none" to job 386.
I [14/Aug/2008:15:01:03 +0100] Job 386 queued on 'KonicaMinolta_BizhubC252' by 'andrewrennie'.
I [14/Aug/2008:15:01:03 +0100] Started filter /usr/libexec/cups/filter/cgpdftops (PID 368) for job 386.
I [14/Aug/2008:15:01:03 +0100] Started filter /usr/libexec/cups/filter/pstops (PID 369) for job 386.
I [14/Aug/2008:15:01:03 +0100] Started filter /Library/Printers/KONICAMINOLTA/filter/pstokmc252 (PID 370) for job 386.
I [14/Aug/2008:15:01:03 +0100] Started backend /usr/libexec/cups/backend/socket (PID 371) for job 386.
The configuration page for the printer did say that Appletalk was disabled. Is this going to be causing the problems? SMB is enabled - can I use that?
Sorry for the delay in replying. For some reason my subscription to this posting disabled?
Anyway, reading your latest log, it appears that the job is being sent from the Mac to the printer. So it does look like the security setting you mentioned in the first post could be the culprit. I know with our Canon copiers, when the Job Accounting is enabled in the copier but not in the driver, the job doesn't print. But there is mention of the job in the log with an error code that shows the incorrect job id/pwd was used.
So I think you need to see if the security settings on the copier can be disabled temporarily to determine if you can print from your Mac. With the settings off, the Mac document should print. If it does, then you know you need to check the Mac driver for a setting that lets you print. If it doesn't, then you will need to look at other things, such as does the machine support PostScript - maybe it is a PCL only printer?
Re the AppleTalk setting, this won't be a problem being disabled. You are using a different protocol. And you could use SMB, however if JetDirect Socket is not working then SMB won't work either as I don't think it's a communication problem.
"But there is mention of the job in the log with an error code that shows the incorrect job id/pwd was used."
This does indeed indicate that Account Track is turned on with your BizHub. If you look at the job log, LCD panel, top left corner, past jobs, you can select the job in question and select the detail button on the lower right corner of the LCD to see the exact reason your BizHub cancelled the job.
You will need to enter an valid login name and password, or just the password if you have the setting selected in Account Track before the BizHub will print your job. I would suggest you entering the fields and then saving it as a Account Track preset so your users don't have to enter the information each time they print. If you need further help with this please respond back in this thread.