Scan to Network folder (possibly SMB issues)

[SpawnTech]

So we have disabled SMBv1 due to the "WannaCry" vulnerabilities. I called HP Support to see if this model printer (Officejet Pro 8630) supported SMBv2 or SMBv3. The tech told me that it support both v2 and v3. (Great right.. I will just enable v2 or v3 and wa-la. Not the case here.)

The way this is setup (when it worked with SMBv1) the folder that we saved scans on a "mapped drive" on our file server. The network path is currently using the IP address of the file server- example- \\10.120.52.193\shared\Scans

I've confirmed that the username and PW being used has all the right access to the folder/subfolders being shared.

I'm not sure what else to check?? Unless that the issue still resides on the original question- Does the officejet pro 8630 support SMBv2 and v3?..

any input would be greatly appreciated!!

thanks!

[sconnary32]

I installed the latest firmware and under networking an improved SNMP setting was available.

I disabled SNMPv1/v2

Enabled SNMPv3

Added an appropriate service account.

Was able to scan to PCs with SMBv1 disabled.

[askariah]

Put port 139 on the priority list; Use fqdn when creating path to the smb share.  

[ttmcmurry]

Hey I believe you're confusing two different things....

SMB = Server Message Block, which has the flawed v1 protocol which is what WannaCry use to spread

SNMP = Simple Network Management Protocol - a way to poll/configure devices for status/commands remotely

HP Printers, both OfficeJet and LaserJet have supported SNMP v1/v2/v3 for a long time. 

However, the scan-to-folder issues are dependent on SMBv1.  HP has not addressed/updated any printer as of the time of this post, so that scan to network can work once more; i.e. issuing firmware to give printers SMBv2 & v3 capabilities.   

My argument on another post asks why is this the case - only a 30 year old deprecated protocol being in use despite very well documented flaws, which were exascerbated by recent exploit attacks via the NSA hacktools that were released on the internet. 

There's no reason why SMB v2/v3 aren't in use in HP's protocol stack other than laziness.  v2 has been out since 2006.  There's very well known open source software (OSS) that provides this functionality with zero cost to HP other than engineering time and testing. 

[sconnary32]

I am not confusing two different things.

I explained what I did to fix the smbv1 issue in my environment after we disabled it.

I made a change to snmp and it worked again.  Why?  Don't know.

[Heriberto_R]

I think the path to the shared folder should be \\10.120.52.193\Scans instead of \\10.120.52.193\shared\Scans.

[MissViv2]

Here's a link to HP's document listing the supported SMB protocol versions for its printing devices. Unfortunately, Officejet Pro 8630 is listed as SMBv1 only.

http://h10032.www1.hp.com/ctg/Manual/c05547920