HP OfficeJet Pro 8600 Scan to Network Folder fails

[starmusic]

For years I had "Scan to Network Folder" working great to my older Windows 10 computer.

I had to upgraded to a new computer which had the newest Win10 updates installed, 

and though the printer in general works great, using the printer's touch screen to Scan to Network Folder fails.

Since the HP software was also updated to "HP Smart", I used that to go to the Settings for 

this feature and did the settings to my new SHARED folder on the new computer

(accessibility on other networked computers confirms it's shared).

I added the Credentials to login to the computer in every possible way, but "Save and Test"

always FAILs with ZERO indication as to why it fails. The credentials are right, and I even

created a new USER named "Printer" on this computer with a new password, and that won't work either.

What's the trick to isolating which part really fails?

Thanks.

[ShlomiL · Accepted solution]

Hi,

There are many possible reasons for such a connection to fail, such as user authentication, a connectivity problem, any share settings issue.

Please clarify what exact error message returns when Pressing Save and Test within its configuration wizard, to better understand any possible cause.

Also, please make sure that SMBv1 is enabled for your computer, the printer require SMBv1 to be enabled to connect to a shared folder, as listed below, with the latest Windows 10 updates SMBv1 is disabled by default:
http://h10032.www1.hp.com/ctg/Manual/c05547920.pdf

From the Control Panel select Uninstall a Program, then press on Turn Windows features on or off and check SMB 1.0/CIFS File Sharing Support among any of its sub-options, then follow the steps on screen to enable the feature and test the profile for the printer again.

Note: Microsoft has released security update MS17-010 that resolves the SMB version 1 vulnerability used by the WannaCry attack, please ensure it is installed on your computer:

https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2017/ms17-010

Shlomi

[starmusic]

Thanks so much!  Yes, it was the SMBv1 issue.  I turned it on, rebooted, and it works great.

Just FYI, I searched for quite a while to see if security update MS17-010 (or KB4013429 or KB401 at all)

was installed, to no avail.  I found a page with 7 different places to look, including the DISM commandline.

I'm assuming that since this new machine was set up with a recent Win10 installer that it includes

the patch to that SMBv1 vulnerability without an explicit KB installed.  Since Windows says I'm all

caught up on updates, I hope it's accurate.

Thanks again for a quick and on-point reply!