Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

FTP accesss through AirPort Extreme

Hi

I have a FTP server on a nas (ProFTPD 1.3.3c Server, Netgear ReadyNAS Duo).
No problems with it until now.
Some FTP clients can not list the folder contents? Strange, do you have a clue?
I think that this problem originates after updating AE to 7.5.2.

Both port 21 and the passive port range are forwarded to the nas.

MacBook Pro 15" (5.3), Mac OS X (10.6.1)

Posted on Dec 20, 2010 2:59 AM

Reply
15 replies

Dec 21, 2010 2:32 PM in response to Elimo

I have the same FTP server configuration, ReadyNAS Duo and AE as Elimo. I too updated from 7.4.2 to 7.5.2. Then all of my FTP clients started reporting passive connection errors and time outs. Here is a proFTPd log snippet where the problem occurs:

Passive data transfer failed, possibly due to network issues
Check your PassivePorts and MasqueradeAddress settings,
and any router, NAT, and firewall rules in the network path.
FTP no transfer timeout, disconnected
FTP session closed.

To fix this issue I simply downgraded back to 7.4.2.

Are any of the Apple AE engineers looking at this NAT issue?

Dec 21, 2010 4:07 PM in response to Elimo

I solved it.

Apple Airport Extreme does not understand the "Masquerade as" field in the FTP settings in ReadyNAS control panel named Frontview.

*The "Masquerade as" field must be left BLANK in order to work with Apples hardware.*

In earlier versions of ReadyNAS firmware (RAIDiator) you could have something written there and Airport Extreme would not care, but after the latest RAIDiator update the field must be left blank.

Message was edited by: Elimo

Message was edited by: Elimo

Dec 22, 2010 4:12 PM in response to Do Right Daddy

I am sad to say that it no longer works.

Right now I don't know why it worked for a while or why it does not work anymore.

It was not the right method. There must be som bugs in ProFTPd.

sorry

I've tried no-ip.com instead of dyndns.org - so far no positive resluts.

http://www.readynas.com/forum/viewtopic.php?f=23&t=48843

Message was edited by: Elimo

Message was edited by: Elimo

Mar 21, 2011 6:14 PM in response to Elimo

This is still an ongoing issue - apple are you listening? If so holla back!

Just bought an aebs to replace a fried linksys router. Figured I would try the sexier look - but seems good looks and brains rarely go together in technology either!

In my situation I am trying to port map 21 to a Windows Server - all other ports are working just fine to this server (HTTP, RDP, SQL) - but FTP is probably the most important one and is currently failing. Local IP/port 21 request works just fine.

How do I downgrade to 7.4.x to see if that works for me? All help is appreciated.

May 13, 2011 8:11 PM in response to Elimo

I have verified this too. I have a synology 209 and when I try to FTP and use a non standard external port (such as 4116) to internal port 21, it won't connect. When I change the port the FTP is listening to on the NAS to 4116...so external 4116 to internal 4116 it works just fine. Pretty lame, but I guess this bug will need to be fixed before I can get it working as expected.


This is my first experience with a pretty severe apple bug. I hope they fix it soon.

Aug 17, 2011 4:03 AM in response to Elimo

I can verify this issue as well. 7.5.2 firmware seems to be the cause, from what I understand of it.


I've got around the problem for now by using a USB drive and sharing that over WAN instead.


Not ideal - surely Apple can fix this one. Its definitely a bug! I can set similar port forwarding/virtual server/firewall configs on pretty much any other router out there. No issues.


I'm running PPPoE on the AEBS and using a dedicated modem off of a copper line. I wonder if maybe that's the problem, the fact I'm running the AEBS with PPPoE? I might try changing to ethernet and having my modem do PPPoA instead and see if that makes a difference. At this stage I can't really be bothered though - I got everyone used to going to the USB disk now.


Is anyone here running their AEBS in ethernet mode got this issue with FTP?


Has anyone out there got an FTP server working through an AEBS with 7.5.2 at all for that matter?


Plenty of threads out there on this issue, so I'm reasonably sure I'm not being thick-skulled on this one....


Anyone out there?

Feb 23, 2012 11:51 PM in response to Elimo

i have the same problem with ftp access from outside. i have a linux based web server for developing websites and realy needed ftp access from outside. after a few times searching, downgrading the firmware of my airport extreme still no success. now i desided to use port 22 over ssh so that i can use SFTP in stead of FTP and everything works fine.


I thought maybe a good tip for others who have this problem.

Jun 28, 2013 9:02 AM in response to Elimo

It looks like many of us are stuck at the same point.

I did make a few tests and I can report what I found out.

When at home, I can connect through passive mode, but from outside LAN, i must connect through active mode.


This was made clear by reading out the connection transcript from Fetch.


Note these two lines:

<< Making data connection to 178.195.122.xxx port 5055 >> Passive mode tries to transfer data through port 5055

<< 200 PORT command successful. Consider using PASV. >> Fetch finds out by itself it must switch to active mode, but hints us about using passive mode


*****************


The transcript:


220 vsFTPd 2.0.4+ (ext.3) ready...

USER admin

331 Please specify the password.

PASS

230 Login successful.

SYST

215 UNIX Type: L8

PWD

257 "/"

CWD Private/

250 Directory successfully changed.

PWD

257 "/Private"

TYPE A

200 Switching to ASCII mode.

PASV

227 Entering Passive Mode (178,195,122,186,19,191)

Making data connection to 178.195.122.xxx port 5055

ABOR

FTP::ftp_abort() FTP_ABOR_SENT_CMD TickCount() = 293912 reply_received = 293912 TickCount() - reply_received = 0

FTP::ftp_abort() FTP_ABOR_SENT_CMD TickCount() = 293913 reply_received = 293912 TickCount() - reply_received = 1

FTP::ftp_abort() FTP_ABOR_SENT_CMD TickCount() = 293916 reply_received = 293912 TickCount() - reply_received = 4

225 No transfer to ABOR.

PORT 192,168,1,58,194,139

200 PORT command successful. Consider using PASV.

LIST -al

150 Here comes the directory listing.

drwxrwxr-x 10 ftp ftp 4096 Jun 27 22:57 .

drwxr-xr-x 6 ftp ftp 4096 Jun 20 14:56 ..

drwxrwxr-x 2 ftp ftp 81 Apr 17 06:45 .AppleDB

drwxrwxr-x 2 ftp ftp 21 Apr 17 06:45 .AppleDesktop

drwxrwsr-x 2 ftp ftp 75 Apr 23 20:48 .AppleDouble


/.../


drwxrwxr-x 3 ftp ftp 25 Apr 24 03:29 Network Trash Folder

drwxrwxr-x 3 ftp ftp 25 Apr 24 03:29 Temporary Items


226 Directory send OK.


Message was edited by: ddelcourt

FTP accesss through AirPort Extreme

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