Officejet Pro 8600 Premium scan to network stopped working

[DavidSMP]

Hi @tkundhi,

Greetings! I have reviewed the post.

I have escalated your concern to HP’s Support Team in your region to have it reviewed for available options if any. 
You should be contacted within 4 business days (Excluding holidays & Weekends). 

Response times may vary by region. 
Please send a Private Message, if you aren’t contacted within 4-5 business days.

Hope this helps.  To simply say thanks, please click the "Thumbs Up" button to give me a Kudos to appreciate my efforts to help. If this helps, please mark this as “Accepted Solution” as it will help several others with the same issue to get it resolved without hassles.

Take care and have a blessed week ahead. 🙂

Cheers!

[allcaps]

Did you get this issue solved?

I have the identical model printer with the same firmware version as yours. The printer has had a wired network connection until about a month ago. Scanning to a network folder on a QNAP NAS on the same network was working fine. However, I had to switch the printer's network connection over to wireless so some wireless devices could use it. When the wireless connection is used, the printer disables the wired connection. When I tried to scan to the network folder with the wireless connection, the scan failed.

The only workaround I know is the one you found.  That is, I created a share on the QNAP NAS that allowed guest r/w access. I then used the HP utility to configure the network connection for the printer using guest as the user with no password. Now I  can scan from the 8600 to a network folder.

[tkundhi]

Hi allcaps,

I spoke to HP escalation team and unfortunately they are unable to provide an reseources to investigate and address the problem due to the age of the printer.  Here is what I think happened.

The latest firmware broke the authentication. After reading your post I rememebered that I too activated wireless networking recently. In my case it was a temporary sitaution and has since been deactivated. However, it was after that event that my scan to network issues began.

I'm not sure if I'm going to replace the HP devices or put in a new NAS. The units I currenly have require authentication. My work around is a bandaid solution. The old Windows XP box I'm currently using as a scan destination runs out of resources periodically and requires a reboot. I've been too busy with the holidays to find a proper solution.

It is disappointing that HP broke a functioning device with an "upgrade" but won't assign a resource to fix it. On one hand I understand their position. Companies can not support products indefinetely. That said I will think about support terms, if and when I replace this device. For now a newer NAS with the ability to have both authenticated and open guest accounts seems to be the best solution for me.

Tarun

[oneboise]

Just to add to this thread....I have the same issue. Thank you Tarun, for doing all of the troubleshooting and sharing the details. I have done essentially the same think with a Synology NAS and a Windows 10 share that work just fine from a plethora of devices. Scan to network has worked from this device for years and all of the sudden will not function. In my case, the OfficeJet is connected to wireless and has been the entire time. I don't want to attempt running a cable to another room just to fix something that should still function.

My firmware version is also CLP1CN1545AR, but again it has been the same for several years. Assuming the printer didn't decide to become self-aware and upgrade itself, that is! This version was released in April of 2016.

I have tried removing and recreating Network Folders to no avail.

If anyone finds a fix or decent workaround for this issue, please share!

[digjoe]

Go to turn off or on features in windows under apps and features of control page. Enable SMB v1( all three boxes) and network folders will start working again. I don't understand why it stopped all of a sudden, mine did too, but this will fix it. Must have occured, (smb turned off),  during Windows update to win10 on my machine!!  HOWEVER WARNING!!!!!!! Microsoft has identified SMB v1 as a known exploit, so caveat emptor!! HP needs to provide us with a firmware update for the 8600 to alleviate this issue!! Peace and good scanning!!

[AlDante]

digjoe, you da man!

Works exactly as advertised.

So easy.  So stupid....  HP couldn't figure it out??  Or be bothered to take the time to figure it out??

What a bunch of lame developers.  Take some pride in your product.  Geesh.

I am now good and happily scanning away wirelessly.

Going to have to figure out the risk of SMB activation however.

Thanks Again digjoe!!!

[digjoe]

Glad it worked for you as it did for me. Supposedly Microsoft security fix MS17-010 fixed that exploit, but many have still disabled the feature as a cautionary step if not needed!! I'm on the fence!!  https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2017/ms17-010. I'm leaving mine as is...WORKING..and believing that the exploit is fixed by the MS17-010 patch!!

[tkundhi]

I'm glad to here some of you found a solution but the root problem is with the HP firmware and how it communicates the login protocol. While you may have found a work around if you are scanning to a Windows machine, the problem prevents scanning to most other devices. The following devices continue to fail.

FAILS

Scan to SMB share on Time Capsule

Scan to SMB share on NAS (several tested) with authentication

Scan to SMB share on NAS (several tested) WITHOUT authentication

Scan to SMB share on Mac

Scan to SMB share on Windows with authentication

Scan to SMB share on linux with authentication

WORKS

Scan to Windows withOUT authentication

Scan to linux withOUT authentication

My ultimate solution was setting up scanning to a raspberrypi (open share) and then a script moves the scan to my Synology. Users can access the scan on the Synology. The raspberrypi is primarily used for other applications and is locked down.

HP in not interested in fixing the bug because the age of the device. They told me so and offered a coupon towards a new device. I declined as it wasn't any cheaper than buying another device on sale from another retailer.

I understand HP position but am still disappointed. They created a bug that require users to disable secuity on their computers for the scan to network functionality to work. Even then it only works with Windows and some linux devices. Sloppy coding. Their response also tells me they don't really care about users security.

[digjoe]

I am not aware of all the senarios that you mentioned and if they are failing from what I know, it's because those devices do not support SMB v1 or have disabled it after supporting it in the past, due to the period of time when it made those units vulnerable.  HP's and Microsoft's position, I believe is that Microsoft security fix MS17-010 fixed that for WIndows but there still rages the position of many that SMB v1 is to be avoided at all costs. I cannot speak to the other OS's or platforms. Now to my knowledge SMBv1 DOES use authentification to login to my WIN10 system. If I do not input proper credentials it WILL FAIL!! I agree that HP should support SMB v2 and v3 so this issue would disappear. Why they do not except in their higher end units is a mystery to me!! They didn't create a bug, Microsoft created a bug within a protocol that they used...fingerpointing approrpiate at this point!! I believe I am understanding this correctly, if not please advise!!

[tkundhi]

Hi digjoe, I tested all those variations as scanning use to work for me and stopped after a firmware update. My initial setup had the HP scanning to an Apple TimeCapsule with a password. I tried scanning to multipe devices in an effort to find a solution. It is not a user/password issue as I tested senarios that require authentications and those that do not. After growing frustrated with the results and the lack of information in the HP logs when the connection failed, I decided to log packets.

Did you review the packet data I posted? The HP printer clearly closes the connection when the remote host is expecting a password. The behavior is the same regardless of remote host's operating system. I find it hard to believe that the SMB code from Apple, SimpleTech, Synology and Ubuntu are all broken. Note, Raspian works without authentication but fails when a password is required.

I'm glad you found a solution. But the problem remains many users, especially those not scanning to Windows hosts.