I have a customer(Bank) that is scanning(to folder) at normal speed and then a print job comes in and the whole machine slows down and prints one then scans one. Back and forth back and forth. I have set Print Priority to JOB ORDER. Customer would like the scans to just finish before it starts to print the incoming job. I have seen some similar posts on this but have found nothing so far to resolve this issue. Thanks for your help!
-
-
Re: Job priority on MP5002
I am think that one of the options for function priority is the current screen function. -
Re: Job priority on MP5002
[QUOTE=slimslob;1222560]I am think that one of the options for function priority is the current screen function.[/QUOTE
It's Display Mode and I have tried that on there MP5002. It makes no difference on my MPC5502a here in the shop. I send a print job while scanning and it never slows down no matter what print priority is set too!?Comment
-
Re: Job priority on MP5002
The other thing I can think of would have to do with network. It seems that auto detect for network speed does not always deliver the best results. I would try 100 full duplex. Considering it is a bank, it might also have something to do with their switch. Maybe talk to their IT.Comment
-
Re: Job priority on MP5002
When Ricoh first came out with the new SMB V2\3 we noticed that the machines started to slow down when printing and scanning at the same time. It was explained to me that it was a limitation of the new firmware.
Writing only supports synchronous transfer, and even if set to asynchronous transfer, the device will still perform synchronous transfer.
Go figure..
2. Limitations
[COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]The SMB version used for Windows authentication is SMBv1. Please use LDAP authentication instead asnecessary.[/COLOR]
- [COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]- The SMB version used for SMB printing is SMBv1.[/COLOR]
- [COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]- Plaintext authentication and LM authentication are not supported with SMBv2/v3.[/COLOR]
- [COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]- In some environments SMBv3 encrypted communication using port 139/tcp is not supportedbecause Windows OS does not support it. The default port setting in the device has been changedto 445/tcp, so there should be no issue.[/COLOR]
- [COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]- Addressing in CNAME using port 139/tcp is not supported. However, it is now supported by port445/tcp.[/COLOR]
- [COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]- Writing only supports synchronous transfer, and even if set to asynchronous transfer, the device willstill perform synchronous transfer.[/COLOR]
- [COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]- Regarding SMB Encryption, the device can communicate using encryption with individual sharefolders but not when encryption is enabled for the entire file server.[/COLOR]
[COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]The following PowerShell command to enable encryption for the entire server is not supported:[/COLOR]
Comment
- [COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]- The SMB version used for SMB printing is SMBv1.[/COLOR]
Comment