Scan to home AltaLink invalid path

[jmmn]

Didn't work. The only permutation that works is the double login I described above.

Scan to Home -> ""Prompt At Device Control Panel", and login with domain\username.

[Joe Arseneau]

Alright, a few more things to attempt

http://<device-IP>/diagnostics/authenticationQuery.php

http://<device-IP>/diagnostics/stripDomainInfo.php

http://<device-IP>/diagnostics/resolveHostname.php

Test each individually, not all in one go.

[jmmn]

Tried it. It made things not work. 

[Joe Arseneau]

Try disabling prepend domain in the DNS settings for the printer

EWS > Properties > Connectivity > Setup > Wired Profile > Edit > DNS

[jmmn]

Thanks for the help Joe. That email filter trick didn't work, but, I've found something that does work. And I'm making sure to Update the workflow templates every time I go to Workflow Scanning.

We are using LDAP authentication for "Log In". I had "Prepend Domain Name" enabled, but I turned it off. Doesn't make a difference.

Then I set Scan to Home -> "Login Credentials to Access the Destination" to "Prompt At Device Control Panel"

So I login as "our_domain\john". Then go to Workflow Scanning, press S2Home, press Scan, get the login prompt again, login as "our_domain\john", and it works. Obviously the double login is annoying. What we would like to happen is for users to login once without having to enter the domain name. Does that make sense?

[Joe Arseneau]

Last thing to try, and do to your scenario, I don't expect it to work, but it might, and I have nothing more to offer, so....

EWS > Properties > Connectivity > Setup > LDAP > Edit > Edit > Custom Filters > Email Address Book Filter > Enable Custom Filter and copy& paste this in there

(|(sn=LDAP*)(cn=LDAP*))

The fact you don't have the user log in makes all my regular bag of tricks seemingly not apply

[jmmn]

Yes we are on v101.001.109.33800.

I set the SMB to use v2 like you showed. I got the same result as before. Also I tried doing Workflow Scanning using the default template (which I configured to point at the same share) and it worked. So the problem must have something to do with the Scan to Home

[Joe Arseneau]

The General release firmware did exactly that which is why I posted the spar, but if you are indeed using the spar firmware I linked, go ahead and eliminate the negotiation by only allowing SMBv2 on the device

[jmmn]

Did the firmware upgrade, no change. Here is what the packet capture looks like. It isn't even trying to do the SMB login, its just doing a SMB protocol request. Then I get the login failed error.

[Joe Arseneau]

First upgrade the firmware.

If it still fails, EWS  >Security > Logs > Network troubleshooting. Enable it, do a scan, download the file and open in Wireshark to diagnose