Hello - I used to be able to scan with no problem when I had Windows 8. I upgraded to Windows 8.1 and now I get a login error 016-782. I'm not sure what I need to change for the settings in the server address book or the shared folder on computer. Any suggestions? Thanks.
Solved! Go to Solution.
Hey you!
I would suggest you try and access the folder from another computer, and see if you can write to it. If not that's the problem.
Other than that maybe try removing your driver and installing the newest one.
If you got the problem when updating, it's probably not a setting on the printer.
Best Regards
Kimzi
--------------------------------------------
Please remember to select "Accept as Solution" for posts that helped you solve the issue.
tashahm2,
I am having the same issue scanning from a workcentre 6505 to a recently upgraded 8.1 system. After a lengthy search of the issue, I found a microsoft knowledge base article confirming this is an issue in the 8.1 release and a fix is planned to be released in November. I guess we just need to sit and wait :(
It is the first bullet point under the known issues section:
http://support.microsoft.com/kb/2883200
Any forum moderators - Can you post as a sticky for others to locate more easily?
Hope this is helpful,
Guy
Hey Guy!
Thanks for the information, gladly the update is due to come out soon then :)
Best Regards
Kimzi
Thank you for that information.
Great news [for my situation anyway], My windows 8.1 installed an automatic update and the scan to network using SMB is now working. No other changes were made.
Good luck to all . . .
Greetings,
You don't happen to have the update number(s) you downloaded yesterday that resolved this, do you?
Thanks,
-AndrewM
Yes, please. That would be very helpful. The issue has not been fixed for me. I still cannot scan documents.
All - my scanner works now. I had to change the settings in the Individual Directory.
Previously:
Login Name = TASHA-PC\Tasha
Share Name = TASHA-PC\ScannedDocs
Currently:
Login Name = Tasha
Share Name = ScannedDocs
I hope this helps!
This issue was addressed by Microsoft in a Windows 8.1/Server 2012 R2 Update Rollup released on November 16th, 2013. The number assigned was KB2887595. More information can be found here:
http://support.microsoft.com/kb/2887595
~Tim