Lanier 525c, Ricoh 2550c, scan to e-mail slow.

[fixthecopier]

Customer said it was fine yesterday. Starting this morning it takes 3 or more minutes to get through. My POC is also the network person for this. he went through and checked everything with the network. I got Ricoh on the phone and we did everything that we could think of.

..Multiple machines, this is the only slow one.
.. Moved to a different location, no change
..Tried sending to a different e-mail server, no change
..No problem with print speed
.. Passes all internal test.
.. The mail server is in the building

Basically I was there over an hour trying different things, everything Ricoh could think of. At the end of it there was no improvement. Ricoh said to try the control board. I feel that boards are good or bad, they don't slow down.

Have any of you had a similar case?

[totoro]

Re: Lanier 525c, Ricoh 2550c, scan to e-mail slow.

The only time I had something like this was when someone set the resolution to the highest and changed it from B/w to color scans.

[fixthecopier]

Re: Lanier 525c, Ricoh 2550c, scan to e-mail slow.

The only time I had something like this was when someone set the resolution to the highest and changed it from B/w to color scans.

I dropped the res to 100 and b/w. No change

[Oze]

Re: Lanier 525c, Ricoh 2550c, scan to e-mail slow.

Latest firmware?
Worth a shot

[slimslob]

Re: Lanier 525c, Ricoh 2550c, scan to e-mail slow.

Clear NCS SP 5810-011. You will have to reenter all IP information. Will also clear device certificates, useful when you screw up trying to create a device certificate and get locked out of WIM.

[fixthecopier]

Re: Lanier 525c, Ricoh 2550c, scan to e-mail slow.

Clear NCS SP 5810-011. You will have to reenter all IP information. Will also clear device certificates, useful when you screw up trying to create a device certificate and get locked out of WIM.

I had tried sp5810-11 while on site. Yesterday morning I went and picked it up, brought to shop to try a different network and got the same results. Had one of the IT guys get involved. It stumped him for a long time. After about an hour, I left to do another call. Came back 40 min later and he had just got it to work correctly. When I ask what fixed it, he said he wasn't sure. He said that he went through it and reset everything he could think of and now it works.