setup scan to network folder yosemite

[TonyAZ623]

Agreed. Read the thread people or create a new one if you do not understand.

The subject of this thread is Scan to OSX folder.... and the lack of SMB 3 support with Yosemite.

[dao1138]

---

@SXH1902 wrote:

Here's the path I've used:

\\10.0.0.XXX\Data\Shared documents\HP scanned docs, where 10.0.0.XXX is the IP address of the Airport Extreme, obtained from Airport Utility.

---

The problem in this thread is NOT scanning to an Airport Extreme using model XXX of your printer.  The problem is scanning to a shared folder on your computer if your computer runs Yosemite.  Which is still NOT supported by most of the printers that have been on the market more than a year. I can scan to a shared folder on my too.

Please go post this on a new thread - you're adding to noise not to signal.

[SXH1902]

I'm running Yosemite 10.10.3.  

The HP OfficeJet Pro 8620 now scans to a shared Network Folder.

Look at the thread title.

Keep whingeing away at HP and me if you like, but this solved the question in the title of the thread.

[jdownward]

I installed the new HP printer software, deleted my old scan folder entry, created a new one using the suggested access string to the shared folder.  Regretably, I am still unable to get scan to a network folder on my Yosemite computer. I am using a wired ethernet connection rather than an airport link from the printer to my computer.  Hence my TCP/IP addresses are a198.168.1.x rather than 10.x.x.x . 

[TonyAZ623]

YES.  We know this.

Guys, the issue has already been CLEARLY identified as the onboard FIRMWARE of the printer does NOT support SMB3 networking protocols.  THUS, you can update and install any HP Software update to your computer and it will NEVER make the printer able to do scan to folder on OSX Yosemite. 

Before this feature will work with Yosemite, HP must get off their bums and write a firmware update for the printer to teach it a trick...namely how to speak SMB3 that Yosemite uses....and prior versions of OSX did not.

I feel like nobody has made use of the countless prior posts where this has been discussed.

[dao1138]

---

@SXH1902 wrote:

I'm running Yosemite 10.10.3.  

The HP OfficeJet Pro 8620 now scans to a shared Network Folder.

Look at the thread title.

Keep whingeing away at HP and me if you like, but this solved the question in the title of the thread.

---

And look at the first message from the thread:

---

I have an OfficeJet 8600 and have been using it to scan to a network folder (on my iMac) for several years.

---

I'm sure newer printers will have their support updated.  The issue is the older models tend to be ignored.

Lurk more.. pop off less.  Just a suggestion.

[SoonerDave]

Unless I'm misunderstanding something, it seems to me that even if SMB3 were the issue, the two devices should really negotiate  a protocol at session initiation. I am dealing with a similar network scan setup issue (not on a MAC) wherein my 8620 *will* scan to one server share, but *wont* to another share on a different server in the same network using the same credentials. It appears that protocol negotiation is at the core of the issue. The odd thing is that it appears an SMB1 negotiation works, whereas an SMB2 negotiation is either terminating unexpectedly without throwing an explicit error or simply failing silently. For a new printer, I would think negotiating SMB2 would not be a problem.

I wish someone from HP would shed some light on this issue; surely someone knows how the printers authenticate to network shares.

[TonyAZ623]

Interesting statement "even if SMB3 were the issue"....

This is really a simple issue.

Mavericks supported SMB2.  The printer supported SMB2.

Yosemite changed to SMB3.  The printer did not change to SMB3.

Yosemite does not provide SMB2 or SMB(1) support.

[SoonerDave]

"

This is really a simple issue.

Mavericks supported SMB2.  The printer supported SMB2.

Yosemite changed to SMB3.  The printer did not change to SMB3.

Yosemite does not provide SMB2 or SMB(1) support."

I will defer to your expertise on Yosemite. ALl I can offer is a post from a thread requesting support for a Yosemite/SMB on a different site that offered a fix of the creation of a configuration file that forced Yosemite to negoitate SMB1 only for connection to certain Windows shares, and the reply that doing so worked even if it wasn't ideal.:

"

You can force connections to default to SMB1 via an nsmb.conf file placed in /etc

sudo echo "[default]" >> /etc/nsmb.conf
sudo echo "smb_neg=smb1_only" >> /etc/nsmb.conf

Probably need a restart in order for this to take effect.

"

Offered FWIW from https://jamfnation.jamfsoftware.com/discussion.html?id=14039

[dao1138]

---

@SoonerDave wrote:

"

This is really a simple issue.

Mavericks supported SMB2.  The printer supported SMB2.

Yosemite changed to SMB3.  The printer did not change to SMB3.

Yosemite does not provide SMB2 or SMB(1) support."

I will defer to your expertise on Yosemite. ALl I can offer is a post from a thread requesting support for a Yosemite/SMB on a different site that offered a fix of the creation of a configuration file that forced Yosemite to negoitate SMB1 only for connection to certain Windows shares, and the reply that doing so worked even if it wasn't ideal.:

"

You can force connections to default to SMB1 via an nsmb.conf file placed in /etc

sudo echo "[default]" >> /etc/nsmb.conf
sudo echo "smb_neg=smb1_only" >> /etc/nsmb.conf

Probably need a restart in order for this to take effect.

"

Offered FWIW from https://jamfnation.jamfsoftware.com/discussion.html?id=14039

---

Aren't there some significant issues with SMB1 regarding security - and you're basically opening a security hole up on your mac by doing that?