gsownsby,
Let me cite part of the slacksite info
arne gave you:
While passive mode FTP solves many of the problems from the client side, it opens up a whole range of problems on the server side.
The biggest issue is the need to allow any remote connection to high numbered ports on the server. Since you do not allow SME, and it's ftp server daemon proftpd, to handle this directly
- you put your own linksys router in between -
those "return ports" are obviously not open
...and you surely didn't forward all "any"

You will find the same information on the proftpd site:
http://www.proftpd.de/Active-Passive_Dokumentation.35.0.htmland more on our problem here:
http://www.proftpd.org/localsite/Userguide/linked/config_ref_PassivePorts.htmlEASIEST solution however is what
charly told you in the other thread ...
remove Linksys and let SME "do it's thing".
- SURE WORKS -
Off the cuff I couldn't tell you why Bullet-Proof does handle the situation ... except that the underlying windows machine must be "very open" to allow this to work! ... which you sort of prove when you "close" Bullet-Proof and it fails!
"ALT-F2" should get you to the commandline (could not find _that_ thread .-) but why not use putty from your (windows) workstation (remember to ssh in)...
Easier to copy and paste into your browser too
- Which SME version ?
- How many NICs ?
- Server only mode ?
- /etc/proftpd.conf ...via putty/ssh
Regards
Reinhold
(note: it doesn't help if you open 2 or more threads
There _was/is_ quite some info in the other thread incl. "an answer"-solution from charly brady).