[Misc] 5052ci scan error 3102 O365

[justanotherhack]

Got past the 4803 errors using TB#117, but still getting an intermittent 3102 error, even when using the "test" button on the webpage. Has anyone seen/resolved this?

[Santander]

Re: 5052ci scan error 3102 O365

Got past the 4803 errors using TB#117, but still getting an intermittent 3102 error, even when using the "test" button on the webpage. Has anyone seen/resolved this?

Is there any other information when the code is displayed, as 3102 is not listed in the service manual. Since it is intermittent, I would suspect that the connection with the server is timing out. Increase the server time out for the SMTP server to 10 or 15 seconds and see if this resolves the problem.

[bsm2]

Re: 5052ci scan error 3102 O365

Turn on client-side 1.0 1.2

[PrintWhisperer]

Re: 5052ci scan error 3102 O365

Turn on client-side 1.0 1.2

I think he means turn off 1.0 and 1.1. O365 doesn't want to connect to a device than can be forced to those insecure protocols in a downgrade attack. 1.2 alone should be good.

3102 has been seen as a TLS session timeout restriction due to generating overlapping TLS sessions when doing multiple scans in short order.

The device doesn't perform scans in FIFO (First In/First Out) but will pause the first TLS session when initiating the next. If you keep feeding and starting new scan sessions, the first one gets old and times out.

The only resolution has been to slow down the scanning. Special firmware was written for the effected customer only in a certain segment of machines but you'll have to contact a rep to chase that down.

[justanotherhack]

Re: 5052ci scan error 3102 O365

Turn on client-side 1.0 1.2

TLS 1.1 on clientside was not checked off. After checking it off, email scanning became much more reliable. Thanks for everyone's input.