Copy Star CS-6002 and Taskalfa 4500 No Longer Scanning O365

[eescamilla]

Two different customers have called today saying they can't scan anymore. Last month we got them switched over to the new legacy O365. Is anyone else having similar issues? Wondering if it's something on Microsoft's end.

[nathicana]

Re: Copy Star CS-6002 and Taskalfa 4500 No Longer Scanning O365

You can try this:

Go into the command center,
Network Security,
uncheck TLS 1.0 and 1.1
and force it to use TLS1.2
Check SHA2
For server side and Client side both

tls settings.jpg

[jmaister]

Re: Copy Star CS-6002 and Taskalfa 4500 No Longer Scanning O365

4500i has that?

[scottybbb]

Re: Copy Star CS-6002 and Taskalfa 4500 No Longer Scanning O365

There is a bulletin about 4803 scan errors when using office 365.

[jmaister]

Re: Copy Star CS-6002 and Taskalfa 4500 No Longer Scanning O365

There is a bulletin about 4803 scan errors when using office 365.

i just checked Astea. Which one?

[PrintWhisperer]

Re: Copy Star CS-6002 and Taskalfa 4500 No Longer Scanning O365

4500i has that?

[eescamilla]

Re: Copy Star CS-6002 and Taskalfa 4500 No Longer Scanning O365

Thank you this worked for the 6002. Although we couldn't check mark SHA2 it was grayed out. Had to use a different server for the 4500 but got that working.

You can try this:

Go into the command center,
Network Security,
uncheck TLS 1.0 and 1.1
and force it to use TLS1.2
Check SHA2
For server side and Client side both

[ATTACH=CONFIG]51075[/ATTACH]

[Samanator]

Re: Copy Star CS-6002 and Taskalfa 4500 No Longer Scanning O365

I had a law office take their 5500i and put a free Gmail account they made for this machine and it worked. I also had a client make a free ZooHoo account for their 4550ci and that worked. I was also told that a mail.com account would work as well. I let all these folks know that it may be just a matter of time before those email services move to TLS 1.2.

I have a couple of accounts that won't let go of their 2560 and 3060 and a pair of 300i. These folks have made special unsecured provisions in their email that operate on ports 25 or 26 and the SMTP server name is an IP address. I guess for those that wish to continue using their xxx0 series machines for scanning to email they will have to do something like that. I also see scan SMB on these devices wil become harder as well.

[fishleg]

Re: Copy Star CS-6002 and Taskalfa 4500 No Longer Scanning O365

Really boils my blood these type of issues.. error cannot connect to server etc to user so they immediately ring the photocopier provider. The error message should say please contact your IT provider unable to scan.

In the UK it's a very gray area if you provide them with a mail server to use your opening yourself up to all sorts of gdpr issues.

I know it's a hard one to draw the line if they have an old machine and you can't fix it with firmware there isn't much you can do no matter how much they complain it's not a problem with the photocopier.

I wish all the manufacturers would do something similar to hp and you can bounce mail off hps servers but on the condition the customer pays for that service. That way all machines would kinda be good to go out the box.

[Santander]

Re: Copy Star CS-6002 and Taskalfa 4500 No Longer Scanning O365

Two different customers have called today saying they can't scan anymore. Last month we got them switched over to the new legacy O365. Is anyone else having similar issues? Wondering if it's something on Microsoft's end.

We switched over a customer to the legacy server on O365 last month and left instructions for the customer's IT people to log in to O365 and set the legacy TLS to true. They didn't do it. Today they call saying that scanning is not working again. Spoke with the IT guy and reminded him that they need to set the legacy TLS to true. After it was set no more problems scanning. Hat tip to Slimslob, this opting in to the legacy TLS must be done by February 2022.