I just deployed 15 ConnectKey copiers to a few medical practices, I noticed that there is a good 4 second delay from then the job is sent from the users computer before the machine starts to print. They came from Ricoh copiers and this was never and issue.
The 5335's dont seem to have this issue, I did some searching, is this a port issue? RAW issue? SNMP issue? Spool issue?
Can anyone help?
To meet Energy saver criteria these devices go to sleep much faster, and therefore first page out suffers.
Connectkey 1.5 (Current) had to have Energy Saver and Power saver reduced from a 4 hour maximum to 30 minutes. By default, the setting is to reduce power 2 minutes after use.
So is this an issue where the printer needs to come out of energy saver and therefore takes longer or is it first page out of a job within minutes of the last job coming out? If the former there is no fix, if the latter.
port should be LPR, not raw, queue name should be lp (Always disable LPR Byte counting)
SNMP should only affect the driver properties opening as it pulls tray /toner info from the machine and should not affect print speed at all.
I can't at all speak to the first out speed of the Ricoh, but pretty much any copier made 5+ years ago has a faster first out page than most current copiers as they did not lower power to reduce run cost or meet standards, In the case of Toner printers, the Fuser stayed at optimal temps so a page could just go through, now the fuser of most products runs warm, but not hot until needed. That tends to be the primary speed reduction, in Solid Ink the ink itself needs to be melted to be fed through to the paper.
There is no Energy Saver off in any current firmware, there is a "no sleep" mode, but low power mode is always enabled, and that reduces fuser power.
The ConnectKey device will do a DNS lookup of the hostname of the computer sending a print to it, every time it recieves a print. The default setting of the device is DNS TIMEOUT of 5 seconds. If you are using external DNS servers in the TCP/IP settings of the machine, you will see a delay such as you are describing. Set the DNS Timeout to 1 second, and if you are using external DNS servers, Googles DNS 18.104.22.168 returns a response that doesnt make the machine angry and go to the secondary DNS for a response.
On the webpage of the machine, properties tab, connectivity setup, in the wired IP Settings area select edit, clink on the DNS Tab. Just below where you enter the DNS servers, is the box for DNS Timeout