FTP No Longer works in High Sierra?

This is the FTP software that I am using. It works flawlessly for me, once I got the settings right. The set-up for me was :

• Create a folder to receive the scans - I created a "Scans" folder on my desktop.

• Go to the System preferences/Sharing and make sure file sharing is on and that "Scans" figures amongst the shared folders with your user having read/write privileges. Others can be Write only (DropBox) if required.

• On my printer, set up an FTP contact pointing to ftp://192.168.xxx.xxx/Scans/ (the address of my computer) and port 2121 in passive mode.

• In the FTP server app, point "Server root:" to /Users/your user name/Desktop (no final slash) and port 2121. I left "Anonymous:" at Read & Write. Other settings to taste 😉. Make sure the FTP server is running.

This is my working setup for an Epson Workforce Pro WF-5620 printer/scanner.

I have two Kyocera Copier/Printers also working with this, although I can't confirm that the settings are exactly the same as they are not on my local network, and I can't access them from where I am at the moment.

Hope this can help you out in some way 🙂

Hi All

I came across this thread after updating to 10.13.2 to discover the very helpful disabling of FTP by Apple and the issue of being able to scan via FTP to our Canon IR C3525i. I tried the FTP Scanner App, using some of the suggestions above, but just couldn't get to work. After pulling my hair out for a couple of hours, I decided to try SMB. I also tried setting up the connection using the Control Panel on the printer itself and was able to make a connection to the Macs by browsing and, would you believe it, a scan appeared on the Desktop/Scans folder!

I saved this entry in the address book and went into the Printers Web Management page on the Mac to check out what settings it had given it. The Hostname was taken from the Mac's Sharing name in System Preferences, with 2 backslashes before and backslashes used for the path:

Host name - \\DOMENICOS-IMAC\scans

This folder was actually on the Desktop, odd that I didn't have to put the full path in...

Folder path was left empty

Username and password as Mac username and password

On Mac sharing, enabled SMB

Went through and did this for all Macs in office and all worked AOK, apart from the last 2 of course. After some more hair pulling, discovered that if you rename the Mac in Sharing prefs and then amend it on the printer, it goes through!

Thought I would add this to the post in case it helps someone else, might save their hair.

Dear Charles,

Thanks for getting back to me. I did try to convert to SMB but no matter what combination of entries I made on my printer, I could not get anything to work. I suspect that the SMB protocol itself on my printer, which has not had any firmware upgrades for 10 years is now out of date and cannot handle modern SMB tasks. There is no way I can see how I can upgrade the firmware on the printer as the manufacturer no longer supports this model, but would gladly take another $15,000 from me to replace my nearly perfect old one. It's only failing is that it has only run through 35,000 pages, around 5% of its anticipated life cycle!

I downloaded an FTP software package and installed it on my server and after 20 minutes got it working. Nice.

Now I can get on with doing work rather than wasting time trying to come to terms with the latest thing Apple has decided to make redundant. I just wish they would talk to some long term users and ask about these major decisions before taking a boardroom executive decision about ageing features. Sure, security is perhaps the reason behind this but I would prefer to be given a chance to balance the relative merits of a theoretical security breach and the frustration of having to ditch a perfectly good machine in order to keep up with someone else's idea of "ideal".

The update software cost $5.00 and the Apple technician struggled to make any impact despite an international call lasting around an hour and a half. It's nice to have a chat but better not to need one in the first place.

The software I used was called FTP Server from langui.net

Cheers

Solved for me using the Dell 3115cn in my case as the scanner. I started with this thread to get to the final solution. I too fell foul of apple removing the FTP capability in High Sierra. I followed advice given here and used the FTP server app, but had a couple of further fixes to apply in my case that may help others. I found the Dell troubleshooting page helpful on the error codes How to Troubleshoot Unable to Scan Over the Network on the 2135cn / 1355cnw / 3115cn / 2355dn / 2145cn / 2155cdn / C3765… This helped me track down the two issues I had in turn. My first issue was a log in issue (016-781 SMB/FTP Error). This actually turned out to be my anti virus firewall blocking the login. Don't know why this wasn't an issue before the High Sierra upgrade but you may need to make sure you allow the connection through the firewall. I turned it off to test in the first instance. Then depending on your software you can tweak from there. Then my second issue was a folder path issue. (016-783 SMB/FTP Error) This was solved using the advice in this thread, by removing the server path name from the scanner settings and only populating in the FTP server app. I Changed the port as advised in this thread from 21 to 5000 (In my case following the Dell allowed range) as port 21 no longer supported. Double checked folders were shared on the mac and remote connections enabled in the sharing settings. Then all was good again. I do hope this helps some of you if still struggling. Matt

The FTP app did the trick for me as well. But there was one wrinkle in setting the root folder. On my Dell MFP 3115cn, it turned out to be necessary only to put the full root directory in the app. When I tried to put anything about the root directory in the scanner itself, the error log reported that the two directories had been aggregated. [In terms of the example above, the system was looking for the path RootDirectory/RootDirectory/Foldername.] As a result, the path did not exist. When I simply left the Server path blank in the scanner, everything worked like a charm. Kudos to the FTP app developer!

Well the information above certainly helped me out, even though I had to sift it a bit to apply to my setup in High Sierra.

I have a networked Epson WF-5620, and my Mac at network address 192.168.10.150.

I set up FTP Server.app to point to /Users/MyAccountName/Desktop as the Server root and left the default port at 2121.

I created a folder called "Scans"(no quotes), on my desktop.

I set up a contact on the Epson using my account details and pointing to ftp://192.168.10.150/Scans/ and port 2121, in Passive mode.

All good 🙂

Hi Tim

On my Konica Minolta Bizhub, the setting for the ftp server app is "path/folder name". But the setting on the scanner is just "path/".

Hope this helps

Thomas

Dear Ogletree,

That is sage advice but there is a catch. If you only have one of anything, it is a bit hard to try things out on a sacrificial machine as a test run. Your advice is spot on but not necessarily practical. It would have been better to carefully study the wording that comes with every update and look for problems likely to happen. Unfortunately, I do not have that much time to study all that comes my way and put it to a test. Not many others would either I suspect.

Another thing, you only notice the absence of mission critical features if you are using it in a mission critical role. Meaning, you would never notice the feature missing if you install on a sacrificial machine because you will not go through every combination and permutation of useful tasks to which the machine is put to. That happens when you use it.

When I ran a computer software company I released trial versions of software updates to clients and closely monitored its behaviour. Any bugs or unexpected consequences were identified, reported, reprogrammed and resolved as quickly as possible. That takes time but no end of testing in an artificial test environment unearths the sort of problems a real live user does. They do the darnedest things, something a tester would not think of doing.

What I object to is an arbitrary decision to axe a feature that is doing nobody any harm and not knowing about it. It's called informed consent.

I've moved on, I have my third party ftp server running and I can happily use my old scanner again, no problems.

Cheers and keep smiling.

somebody else commented on that FTP on High Sierra

you can let apple know using their feedback channel Feedback - macOS - Apple

Hi,

I have the same problem with an OKI printer-scanner. I've tried using the app 'FTP Server', but couldn't make it work, not even with help from the app developer. When you say 'took some setting up on the hardware end of things', what do you mean exactly?

Thanks,

Jiri

I have the same problem. I have a Fuji Zerox Docucenter CS2020 and cannot scan to a shared folder on my desktop. And the scanner breaks larger scanned PDF documents up in 3 pages files and sends multiple emails painful.

You guys rule.:) this solved my problem with scanning on my Konica Minolta Bizhub 253 on MacOS 10.13 . thank you so much. I tried with no luck for 2 days to setup scan over SMB. but FTP work now and I can scan. thank you so much. If anyone knows how i could scan to my My Cloud EX2 Ultrait would be great. So i can access the scan files from anywhere.

Thank you Tim for your so precious help. I had twice technicians from Konica who came and told that there is no way to solve the problem. Your solutions, the app and this configuration, just saved me. So a warm thanks for you help. Regards.