Cannot upload via FTP — "152 Gimme the file please."

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Launch Frotz.
2. Tap the "info" icon at top.
3. Select "File Transfer".
4. Tap "Start File Transfer Server".
5. FTP to the displayed IP and port, using the displayed user name.
6. Attempt to upload any file to any directory.

What is the expected output or behavior?  What do you see instead?
Expected file to upload.  Instead, get immediate error message "152 Gimme
the file please." using Windows XP SP3's built-in command-line FTP client
or "Copying files to remote side failed.\nGimme the file please." after
several seconds of apparently-successful transmission using WinSCP 4.1.9. 
In either case, a zero-byte file with the appropriate name is left behind.
 Was able to reconnect with WinSCP and delete these files without issue.

What version of Frotz are you using?
1.3

What version of iPhone/iPod Touch OS? (2.0, 2.1, 2.2.1, 3.0, etc.)
iPhone 3G — model MB704LL
iPhone OS 3.1 (7C144)

Please provide any additional information below.
Connected via 801.11g using WPA2 security.  Device is *not* "jailbroken".

Original issue reported on code.google.com by dark.ry...@gmail.com on 3 Oct 2009 at 4:00

[GoogleCodeExporter]

It's possible this could be caused by Windows firewall settings.  Normal FTP 
uses something called "passive 
mode" where when you transfer a file, the FTP server actually initiates a data 
connection back to your ftp 
client in order to transfer the each file.
It's possible a firewall setting is preventing this connection; the other 
possibility is that the ftp client is trying 
to use active mode instead, which isn't supported, but that's unlikely since 
passive is supposed to be the 
default and WinSCP is also failing.

The "152 Gimme the file please"  (really, just the 152, the rest of the string 
can be anything) is a normal part 
of the FTP protocol and not an actual error, but you should also see a PORT 
command printed before that, and 
a progress bar of the actual file transfer right after it, followed 226 File 
transfer successful.

I only have a Visa  Windows machine to test this with and it works fine for me, 
but if you continue to have 
problems I can find an Xp machine at work to try to reproduce it.

Original comment by spath...@gmail.com on 4 Oct 2009 at 2:53

[GoogleCodeExporter]

No further feedback from user; closing as not reproducible.
Will re-open if necessary later.

Original comment by spath...@gmail.com on 12 Oct 2009 at 6:46

• Changed state: Deferred

[GoogleCodeExporter]

I had the same problem with WinSCP on Windows XP. I turned on passive mode in 
WinSCP 
and it worked fine. Not sure why that is not the default for WinSCP. 

Original comment by jake.don...@gmail.com on 12 Nov 2009 at 5:41

[GoogleCodeExporter]

Thanks for letting me know that.  I thought passive mode was the default in 
pretty much all ftp clients and never 
tested active mode in my ftp implementation.   I'll see if I can get it working 
for the next version, or else 
mention that you have to use passive in the ftp instructions.

Original comment by spath...@gmail.com on 12 Nov 2009 at 7:54