iR-ADV C2220 showing " ssl error (smtp tx)" #841

[lokeshpatidar]

Hello,

Suddenly, iR-ADV C2220 is showing SSL error (smtp TX) on screen. It was working fine for up to 1 year. I check the logs I found #841 error code.

Help?

[Crow]

Were you by any chance trying to use a gmail account when getting this error? We just had a machine start throwing this error as well and it has been working fine. We also have two of the same copiers that have the exact same settings, one fails, the other does not. Just trying to nail down where this is occuring.

[chuckintex]

Were you by any chance trying to use a gmail account when getting this error? We just had a machine start throwing this error as well and it has been working fine. We also have two of the same copiers that have the exact same settings, one fails, the other does not. Just trying to nail down where this is occuring.

This is my scenario exactly. have some machines that do work, some that don't. all worked fine yesterday afternoon. this morning, 2 of them won't. all scan to gmail account (same one). ISP is Comcast fiber (xfinity).

[charm5496]

the latest firmware updates have been resolving the gmail hosted scan to email issues lately, and make sure the machines are on port 587

[jlee]

Just to reiterate what charm5496 said, please make sure you're using port 587 and not port 465. Google is phasing out SSLv3 and RC4, so we should be using TLS moving forward.

On our IR-ADV c5250, I had to change the port in Level 2 Service Mode.


1. Press "Settings/Registration".
2. Press 2 and 8 simultaneously.
3. Press "Settings/Registration" again.
4. Choose "Mode List".
5. Choose "Copier".
6. Choose "Network".
7. Press "Level 1" to get to "Level 2".
8. Press "SMTPTXPN".
9. Change port from 465 to 587.
10. Hit OK.
11. Hit "Reset" until you fully exit.
12. Reboot copier (not sure if necessary, but just in case).

[lokeshpatidar]

we are using gmail account. now the machine is working fine since we have just changed smtp port number to 587. before the port was configured 465 it was not working.

thanks

[chuckintex]

the latest firmware updates have been resolving the gmail hosted scan to email issues lately, and make sure the machines are on port 587

thanks! will go try this straight away!

[kcolvin]

Just to reiterate what charm5496 said, please make sure you're using port 587 and not port 465. Google is phasing out SSLv3 and RC4, so we should be using TLS moving forward.

On our IR-ADV c5250, I had to change the port in Level 2 Service Mode.


1. Press "Settings/Registration".
2. Press 2 and 8 simultaneously.
3. Press "Settings/Registration" again.
4. Choose "Mode List".
5. Choose "Copier".
6. Choose "Network".
7. Press "Level 1" to get to "Level 2".
8. Press "SMTPTXPN".
9. Change port from 465 to 587.
10. Hit OK.
11. Hit "Reset" until you fully exit.
12. Reboot copier (not sure if necessary, but just in case).

Hi Guys can this be changed at the web browser or will it need eyes on the machine?

Thanks
Keith

[chuckintex]

Hi Guys can this be changed at the web browser or will it need eyes on the machine?

Thanks
Keith

must be at the machine. these configuration options not available "remotely".

[chuckintex]

Just to reiterate what charm5496 said, please make sure you're using port 587 and not port 465. Google is phasing out SSLv3 and RC4, so we should be using TLS moving forward.

On our IR-ADV c5250, I had to change the port in Level 2 Service Mode.


In my c5045 and my ir4035 and 4025 there was a step between the 5 and 6 as this was written(the option selection), I corrected for my experience.

1. Press "Settings/Registration".
2. Press 2 and 8 simultaneously.
3. Press "Settings/Registration" again.
4. Choose "Mode List".
5. Choose "Copier".
6. Choose "Option"
7. Choose "Network".
8. Press "Level 1" to get to "Level 2".
9. Press "SMTPTXPN".
10. Change port from 465 to 587.
11. Hit OK.
12. Hit "Reset" until you fully exit.
13. Reboot copier (always reboot when changing network settings).

And yes, as with the others, this totally worked for me. I have 7 of these total, all had 465 port. 2 stopped working at the same moment. this was the fix. I'm waiting to see when/if the other 5 also have this issue. 3 of those are older and 2 are same generation as these.