Scanning to SMB error

I have a scanner/copier that can scan directly to a folder on my computer using SMB. This worked flawlessly before upgrading to Mavericks. This is what the scanner interface looks like.


User uploaded file


No file shows up in the specified folder and The scanner has a cryptic "TO FILE ERROR". I'm wondering if it's related to the SMB2 issues others are having. I've turned off the firewall. I've tried various syntaxes. I'm out of ideas. Anyone else have any similar issues?

MacBook Pro, OS X Mavericks (10.9)

Posted on Oct 31, 2013 11:42 AM

Reply
10 replies

Nov 23, 2013 2:34 AM in response to Rogers 4-4-0

hi.

why dont you switch on your ftp scanning ( sudo -s launchctl load -w /System/Library/LaunchDaemons/ftp.plist ) in your terminal window. Go to your home folder, add a Scans folder . Go to your copier and setup a ftp scan instead of a smb scan. This would be a xerox E.g

At copier address book, input....

1 - FTP

2 - your I.P address

3 - Share name - which is Scans

4 your login

5 Your password

Nov 30, 2013 6:56 AM in response to dechy12

FTP is much less secure. Your password is sent in unencrypted text as I understand it. When Apple went to 10.7 they abandoned the standard SMB so scanning was not working with SMB and the easiest workaround was FTP. However, now that they have brought back compatible SMB in Mavericks it seems foolish to use FTP.


Message was edited by: GBH

Mar 13, 2014 9:39 AM in response to mescas

The overall issue of multi-function-printers not being able to scan to an SMB share on a Mac server relates to when Apple switched to using their own SMB software called SMBx instead of the previously used open-source Samba software.


This change was caused by the Samba project moving to a GPL3 type license which Apple felt they could not agree to. Apple made the switch when they released Lion aka. OS X 10.7. Prior to that Apple had stuck with an older version of Samba under the GPL2 license but had fallen further and further behind the current Samba versions as a result.


With SMBx Apple wrote their own solution from scratch and was able to add new features like compatibility with SMB2 which newer versions of Samba are also compatible with. However Apple did also fail to implement some other features. One of these was the ability to act as an NT style Primary Domain Controller (PDC) or even a Backup Domain Controller, and similar older less secure types of Window authentication also got lost. It is these losses that caused most of the compaibility problems with MFP scanner type devices although the SMB2 vs. SMB1 difference has also had some impact.


Apple has gradually improved things but overall the situation remains unchanged even with Mavericks, however it is also the case that makers of MFP devices have now been aware of this situation for some time and some of them have issued new firmware to get round these issues.


Therefore you should see if there are any new firmware updates for your MFP that may help or the only other options are as follows -


  1. Use a different protocol, some MFPs support FTP and/or email as options and yes particularly with FTP there are security concerns
  2. or use a different server for the SMB share, this could even by a virtual machine (running on a Mac) using a shared folder on the Mac and then serving it via Samba or of course you could use a 'real' Windows server
  3. or you could look at installing yourself the Samba software on the Mac and 'replacing' Apple's SMBx software, see SMBup at http://eduo.info/apps/smbup

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Scanning to SMB error

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.