scan to network folder (linux & mac)

[Bradrh]

I'm trying to get 'scan to network folder' working for a folder on linux.   I have samba share setup &  a mac on the network can connect, so it must be working.

I'm using Embedded Web Server to set this up.

The samba folder is /home/username/Sambashare, the folder I want to scan to is /home/username/Sambashare/Scans

What is the format needed for the network path?

I've tried several ways to describe the

\\ipaddr\home/username\Sambashare\Scans

\\ipaddr\Scans

\\computername.local\Scans

\\computername.local\home\username\SambashareScans

I can't get past 'Network error. Check the printer's network connection and try again.'

What am I doing wrong?

[Garp_senchau]

@Bradrh,

Thanks for reaching out to the HP Support Community! 🎉

I’m here to help you troubleshoot your issue and get things back on track. Just follow these steps below, and we’ll have you running smoothly in no time:

You may refer these guides to setup scan to network folder:

• Set up Scan to Network Folder
• Scan to a network foldera

I’m pretty confident this will do the trick! But hey, if you run into any bumps along the way or need a little extra help, just give me a shout! I’ve got your back. 💪

Also, if this reply solved your problem (or made you feel like a tech wizard 😎), please click "Accepted Solution". It helps others, and I promise I’ll do a little happy dance. 🕺 Also, if you could click 'Yes' under ‘Was this reply helpful?’—that’s like giving me a virtual high-five. 🙌

Thanks again for being awesome, and I hope you have an amazing day ahead! 🌟

Cheers,

[Bradrh · Accepted solution]

I read those docs several times.      It didn't work using my computer name.   I had to use a static ip and use that ip address

[MichaelBMorell]

Hi All. As most of you, being unable to use "scan to folder" because of invalid credentials has been a very frustrating experience. (If you want to skip the commentary, just look for the items in bold and red text)

Imagine though how frustrating it is for me; an actual Information Security Professional with over 25+ years of intimate knowledge of networking and a very long alphabet soup of letters after their name. To being able to read raw packet captures and understand SMB and authentication at the most discreet level that would make mortals heads explode (yes, I actually fired up a packet capture to see what was going on "under the hood" and poured over windows event logs). When *I* can't do the most rudimentary and basic task like scanning to a network folder, it is not just beyond humiliating. It is literally soul crushing.

With that said: I recently made the switch from win10 pro to win11 pro (clean install). And things broke.

So, what is the fix? I found two possibilities: the Main culprit "username and password". The second, Share/NTFS permissions.

For whatever reason, and please do not ask me why, I did not create the HP OS. When the HP sends over the creds, windows was not able to interpret any account over 4 characters and any password over 6 characters. So, I applied the KISS method (keep it simple stupid).  I made a 4-character username and a password of 123456  
(I originally tried 1234567 which is part of the old lanman hash padding avoidance trick, but that is a different discussion).

Next, set up your share. Find the folder you want to share out and do 2 things.

Set Permissions: Sharing Permissions and NTFS permissions are different.
1. Add the user DIRECTLY to the NTFS permissions and grant them full control (this violates every principle I have in my body, but it was the only way). 

2. In sharing permissions, "ALWAYS" put "Everyone - Full Control".

Why everyone full control? Because you want to control permissions at the NTFS level and not Sharing permissions level. Trust me on this, it will make your life easier.

With those two key items out of the way. Load up the HP Web Console.

When in the HP Web console, go to the scan/network folders area; just use the UNC path to the share \\IPaddress\ShareName

In the U/P, just use the simple username, and the simple password. No need to "domain qualify" it because it is going to be a local user on the machine.

If for some reason you don't know how to create a user account on windows home, the best I can tell you is to look at this article.
https://www.makeuseof.com/windows-home-edition-enable-local-user-group-management/

For windows pro users, use computer managements "Local Users and Groups".

This *Should* work without having to enable SMB1/CIFs on the computer or changing the SMB bindings on the printer.

As long as it is saying "invalid credentials", it means it is talking to your computer, but your system is not recognizing it.  If it says anything else, then it most likely your windows firewall or a bad unc path or you did not share out the folder.

Now I know I said, "don't ask me why", but from what I can tell (this is more for the HP dev team and other nerds), whatever the printer is sending over for NTLM Creds, it is getting mangled when it is beyond those characters limits. Packet captures and event logs don't lie. SMBv3 negotiation at the packet capture level is working perfectly okay.

The Windows Security logs though was complaining about NTLM, with a very weird version that I have not seen before:

"NT    LM .012"    and a 0 key length.

It should be "NTLMv2" and a key length of 128.

So, this is why I said don't ask me because I have no idea where that weirdness is even coming from. In the packet capture, the WinOS sends back an immediate RST packet to the printer when the u/p is above the 4/6 character limits. Which it rightly should when it sees such gibberish.

Now if I was a betting man, (again, HP Dev Team), check your implementation of NTLM and make sure it is able to negotiate correctly.

(Further nerd out) Back in the old days when dinosaurs roamed the earth, there was something called the "LANMAN Hash". This was a gold mine for us "ethical hackers" when sniffing the network for passwords to crack. Because in the old timey LANMAN world, a password is broken into segments of 7 characters.  Anything less than 7 will add a padding of 0.  So, if you have a 4-character password, it pads the end of it with 3 zeros.  If you have a 10-character password, it splits it up into the first 7 and then 3 with 4 pads.  You can hopefully see why it became pretty trivial to crack a password, especially over SMBv1 that has very weak encryption.  LANMAN was replaced with NTLM and then NTLMv2.   That removed our gold mine (but we have other ways of exploiting weaknesses in NTLM)

So, there you have it folks, from your friendly neighborhood CISSP CEH CCSK CCNP RHCE MCSE+I