Thanks for all the info folks!
I am familiar with all these processes.
Now I think I know what it is:
You can scan to Windows 10 Home with a PIN.
You cannot scan to Windows 10 Pro with a PIN. It has to be a password. Can anyone verify this?
Now I have an issue changing the PIN to a password, which is a separate problem. The option to remove it is not there. I am working on that with the customer. Also their secondary confirmation email with Microsoft is gmail and it is full so we cannot get a confirmation. When the customer deleted some old emails it still did not allow him to receive, so we are waiting for gmail to catch up and then I will go back. Major pain all these scanning issues! At least the with new machines the customer can update their firmware themselves! But that still won't resolve the turning off of network sharing when there are major updates...
This is very bad advice: there are multiple security issues with SMB1 and if you turn it on and a customer gets hit with an vulnerability related to it that falls on you.
This model supports SMB3 with firmware updates as has been noted already.
Most of the issues with scanning on non-domain Windows machines come down to the person being signed in with a Microsoft account as opposed to a local account. It's often best to create a local account for scanning, even if it's not the one the user logs into the computer with, as long as it has access to the share folder and the same credentials are used on the MFP it will work.
In Control Panel - System - Workgroup on the Windows10 Pro are they set to the same WORKGROUPname as the win10 Home computers or are they set to a DOMAIN name? Domain computers will not accept fie transfers from non domain devices. If all 3 WQin10 Pros are set to the same domain name, try setting the C2003 to the same domain, not workgroup, name, then set one of the Win10 Pros as the first DNS and try scanning by device name not IP address.
Bookmarks