SMB scanning in Windows 10 Azure Active Directory environment

[progoffice]

Has anybody run into SMB scan issues on Windows 10 in an Azure Active Directory environment? I was setting up a Konica Minolta C458 and kept getting a "Login Error" no matter what Windows 10 password/pin combination I used. I verified that the login credentials I had were correct, but no matter what I entered - "Login Error". I created a local account on the same computer and it worked fine. Since this is cloud based active directory, perhaps something else has to be done to authenticate the user. I came across this post Access Samba Shares With Windows 10 And Azure Ad Setup – A Stack of Notes as a possible solution, but it didn't work for me. I think it's on to something, but I may not have set it up correctly. Any help would be appreciated.

[slimslob]

Since you can scan to a local folder, the problem might be a timing factor on getting a response back from the cloud. If the KM does not receive an ACK response within a set time frame it assumes an error.

[MFPs R Now PCs]

This was a while back when I read this information and there has been a couple of "thresholds" that have been applied to Windows 10 but I believed that one could only "scan" to a Windows shared folder using SMB when using a local account (that it was required).

[gkalchik]

This was a while back when I read this information and there has been a couple of "thresholds" that have been applied to Windows 10 but I believed that one could only "scan" to a Windows shared folder using SMB when using a local account (that it was required).

This has been my experience.