MF743cdw Scan to Destination (SMB) not working

[fmood123]

For the life of me I can't seem to get the Scan to Destination to work consistently.

I have a NAS that I want to scan the files to, I have the share setup, password correct, can connect from 2 different computers to it, it even worked 2 times from the printer, but nothing changed just some time passed and it doesn't work. I tried restarting both he NAS and the Printer but nothing works. Status code. 801

HELP ME!!!!!

I also thought this had an application library app for cloud apps like google drive/dropbox/etc, however I don't see that where is that, I would love to be able to scan to dropbox or google drive! PLEASE HELP!!!! I really need this to work!

[Dubbs777]

Hi,

   I'm ansering this post a bit late but it as it took me 3 hours to solve the issue, I wanted to share with future readers.
   I have a MF8500C Series with QNAP NAS and SMB suddenly stopped working.

   The issue is related to the SMB version used by the printer : Canon 8540 printer is using SMB v1 to connect to NAS (even with the latest Canon firmware)

    As SMB v1 is known to have critical security issues, QNAP changed the defaut settings to forbid SMBv1 by defaut and require at least SMBv2 in their recent updates. I found out by activating SMB login logs on the QNAP.

   Here is the way to re-enable SMBv1, knowing there is a security risk : https://www.qnap.com/en/how-to/faq/article/how-to-enable-smb-v1-for-qts-426433434 (check your NAS model and/or version)

[shadowsports]

Hi Dubbs777,

This would work, and its true SMBv1 has been deprecated in QTS.  Re-enabling is not that big of a deal since even QNAP states do not expose your NAS directly to the internet.  A layered security approach is always recommended.     😃

[jpo]

fmood123, did you ever find a solution? I'm having a similar problem.

On my MF644C, I used to be able to scan and save via SMB to my Synology NAS. In the past couple days, 2 scans out of maybe 20 attempts were successful. I'm getting an 801 error.

[fmood123]

I gave up, because I do think they are right that it's because it's smb v1 which is known as insecure. Cannon should update it but...they haven't!

[jpo]

Thanks for the reply on this old thread. For the record, for anyone else searching for this in the future, enabling smb v1 didn't even work for me, and that seemed like an unlikely solution for my case anyway, since it has worked in the past day (ie, it doesn't seem like without smb v1 enabled, that my NAS would occasionally decide it's ok). In any case, I'll likely post an update here if I happen to find a solution that could be useful to you or others.

[fmood123]

Thanks! Appreciate that. I kinda felt that way with what you were describing as it worked a few times, not like an update that shut off smb 1 and then it stopped forever. So I don't know your setup but are you using ip's or domain names? Could it not be performing the lookup properly all the time? IP confusion like an overlap? Just some random thought! Good luck!

[jpo]

I was using a domain name. I just switched to IP address, and it worked 3 out of 3 times. It seems you just solved my problem. Thanks so much for your help. I'm sorry I can't help you with yours, but I hope you can feel good about ending this frustration for me.