ftp passive mode messed up?

[saint.duo]

OK, I have an ftp server running on a machine running 10.1.3. It is behind a router, but it has a translated IP for it. (real IP = internal IP of the machine), and it works fine for web, afp, remote desktop and most ftp functions.

in the terminal, if I connect to it from home, and switch to passive mode, and start changing and ls'ing directories, it will randomly disconnect me due to an error.

if I use a program called "screen dump" to try to upload to it, it will get stuck at "setting passive mode (serverip,0,ftpport)".

any ideas anyone?

[methnen]

The only thing I can think of is that it is possibly a port that I should be opening up. I talked with Panic the makers of Transmit (an ftp client) cause I thought it was their app. They couldn't seem to find the problem though. Anyone else having this same problem. Oh I too am behind a router with port 21 mapped to my computer.

Jamie

[saint.duo]

strange... my FTP server uses port 21.

My port mapping is supposed to be complete/absolute, though. The ONLY machine that this specific real IP points to is my machine through the router.

Wonder if it's the router doing it.

EDIT

LOL. I'm a Triple-A-Player now! This is my 50th post!

[Novajo]

Is your firewall activated ? Just curious. If it is, then maybe it times out because of it.

[saint.duo]

I'm currently in the process of testing to see if it's the router messing it up, on the server end, or the NAT system that I'm behind messing it up on this end.
I'll post what I find out.

[methnen]

As I am having the same problem and it sounds like our reasons may be the same. :)

Jamie

[saint.duo]

Well, it's either our router at work, which I doubt, since every other service works fine, or it's Mac OS X's implementation of FTP.

I suppose the only real way to test this would be to install Rumpus in 9, and see if it still happens connecting to the same machine booted into 9.

Luckily, it's not my NAT setup at home that I'm behind.

[Novajo]

I need to understand a little better your setup:

is it this:

Computer at work with FTP server
router at work
(firewall?)
internet
Computer at home (OS X 10.1.3) with external, accessible IP
firewall
natd
(internal/other machine ?) with mapped IP (say 192.168.0.1)


Who is connecting to what ?

Where is the firewall? Do you have one between work and world as well as between you and world ? If you have two, I can see why you have a problem.
(As a workaround, you could use scp localfile username@remote.machine:)

[methnen]

My setup is this.

Computer with FTP server-->Asante Router-->DSL Modem-->Outside world...

The Asante router and the DSL modem both have firewalls. The modem is set to pass all calls on port 21 to the Asante Router. Then the Asante router is set to send all calls on port 21 to my computer. It does allow people to connect, just not with a passive connection.

Jamie

[saint.duo]

My Home Computer -> NAT setup -> DSL -> the world -> T1 -> Router, machine is direct mapped all IPs through to -> my Work machine

test I did to narrow it down to the "right side" of the world

Coworker's home computer -> business cable -> the world -> T1 -> Router -> Work Machine

I can connect via passive mode (except with screen dump), but when I start changing directories, ls'ing, etc, I will get booted after around 5 commands.