Impossible scan to folder (smb).

[lahreche]

hello

i followed the procedure to scan on a folder (smb). 
but on the printer I have the message "connection error".
I shared my folder and I gave all the rights.

really i do not know what else to do ?

thank's

[Joe053204-hcl]

lahra2 is not equivelant to LAHRA2INS.So those 2 screenshots don't relate

Follow this post to get it right.

Use this firmware if needed

[lahreche]

thank you, but even if i use the account lahra2ins it doesnt work.
from another pc I check that the file was accesible since everyone can access it.

moreover the account lahra2 is the owner (proprietaire).

[lahreche]

my session is in a domain, it's not a local session.

in the user name, must i put lahra2 or lahra2@snclavalin.com ?

[lahreche]

sorry but i want to use the adress book because i have some 50 users and it's more easy for theme to use the adress book to scan.

[Joe053204-hcl]

My linked post shows exactly how to get the username in proper formatting for every single scenario that can exist.

[Joe053204-hcl]

 It's still exactly the same settings required in exactly the same order.

[Patrick8]

This is a standard setup that we do for a lot of our users and this is the first time I've seen this issue.  I'm inclined to blame the Fall Creators Update, but want to be sure I haven't missed a step somewhere, or there isn't some other update or something that could be causing this.

[lahreche]

thank you for your help

when i creat a new model, i have this page

also how to add a person in scan to mailboxes (hard disque of the printer)

[Joe053204-hcl]

There is no chance the Fall Creators update is in any way relevant, the steps I provided work on literally every OS that exists today for SMB on the firmware that I linked for your machine if you follow the steps I provided. If you are using a DFS (Which you are not) there is another step that may have been needed, but that isn't worth going over because it isn't in any way relevant here because it doesn't apply to Windows 10 at all.

If you want to firmly place blame, start with the wireshark trace, which is done in the webui (CWIS) of the printer and filter it to port 445 to see all traffic between the printer and the PC.