Hi!
Hoping someone knows how to solve this.
We have an issue which we have just confirmed to happen with both Ricoh Aficio MP201 printers at this location.
I suspect a language issue? Don't know if it's with the documents being sent or the printers!
Printing from Windows applications is fine with both setups; this makes me think that having drivers on the computer to translate the code is bypassing the error.
It is a problem printing through CUPS - when the printer is plugged in to the wall and set up to use port 9100. The error happens with the accounting application that outputs PCL and it happens to postscript test printing via princonf. CUPS shows "printing ..." but nothing comes out of the printer, or else at one point during our testing, we were getting an almost blank page with something about PJL on it. Eventually after the 300sec. timeout, we get the error in the system log for the printer: diprintd: "diprint data send timeout ERR". When it is set up this way, it will print out from any users' desktop applications without issue, including post script files! Text file test via printconf works fine. I have set diprint both thru the Web Image Monitor interface and via telnet (and logged out and yes'd to save).
And when the printer is plugged in via USB to a computer and set up in CUPS to use LPD port 515, everything prints fine.
We've got Kyocera, HP, Dell, and Xerox all with the same CUPS setup - some were 515, some 9100, all have been switched to 9100 now and none of them have this issue.
They even had one of the printers replaced by Ricoh a couple of years ago in an attempt to solve this. The copier tech claims it's a network issue; I wouldn't think so since it's not just stopping at the CUPS queue, it looks like some of the data is actually reaching the printer. I don't see any evidence of firmware for these units on the Ricoh support sites.
They're about to cut-over to an IBM AS400 accounting app. All of the printers must be networked via 9100, no possibility to have some printers go thru Windows anymore... are we likely to have the same issue with the new app?
What settings could be erroneous? Is there a driver we can put on the CentOS machine hosting CUPS?
Hoping someone knows how to solve this.
We have an issue which we have just confirmed to happen with both Ricoh Aficio MP201 printers at this location.
I suspect a language issue? Don't know if it's with the documents being sent or the printers!
Printing from Windows applications is fine with both setups; this makes me think that having drivers on the computer to translate the code is bypassing the error.
It is a problem printing through CUPS - when the printer is plugged in to the wall and set up to use port 9100. The error happens with the accounting application that outputs PCL and it happens to postscript test printing via princonf. CUPS shows "printing ..." but nothing comes out of the printer, or else at one point during our testing, we were getting an almost blank page with something about PJL on it. Eventually after the 300sec. timeout, we get the error in the system log for the printer: diprintd: "diprint data send timeout ERR". When it is set up this way, it will print out from any users' desktop applications without issue, including post script files! Text file test via printconf works fine. I have set diprint both thru the Web Image Monitor interface and via telnet (and logged out and yes'd to save).
And when the printer is plugged in via USB to a computer and set up in CUPS to use LPD port 515, everything prints fine.
We've got Kyocera, HP, Dell, and Xerox all with the same CUPS setup - some were 515, some 9100, all have been switched to 9100 now and none of them have this issue.
They even had one of the printers replaced by Ricoh a couple of years ago in an attempt to solve this. The copier tech claims it's a network issue; I wouldn't think so since it's not just stopping at the CUPS queue, it looks like some of the data is actually reaching the printer. I don't see any evidence of firmware for these units on the Ricoh support sites.
They're about to cut-over to an IBM AS400 accounting app. All of the printers must be networked via 9100, no possibility to have some printers go thru Windows anymore... are we likely to have the same issue with the new app?
What settings could be erroneous? Is there a driver we can put on the CentOS machine hosting CUPS?
Comment