No FTP client working under OSX

mehronx · 05-14-2003, 11:06 AM

I've been having an issue where I cannot connect to FTP servers under OS X.

Whether I use the terminal ftp client, Transmit, or Fetch, the client hangs after connecting while "Receiving file list". I've tried both passive and non passive mode with no luck.

I believe that if I let the client continue to try, I get "Data connection could not be made."

Mikey-San · 05-14-2003, 11:12 AM

I know you've mentioned passive vs non-passive, but did you set that in the FTP app or in the OS X system prefs? (If you're behind a firewall, you'll need to use PASV mode to use FTP.)

mehronx · 05-14-2003, 11:18 AM

I'm behind a router with Network Address Translation I believe it is called.

So my client and my system config should be under Passive mode?

What is Passive mode by the way?

Gimpy00Wang · 05-14-2003, 01:05 PM

First, let's talk about non-passive... non-passive (normal) FTP uses two ports: 20 & 21. Port 21 is used for the connection and authentication while port 20 is used for the transmission of data.

Now, about passive. Passive FTP still uses port 21 for the connection and authentication, but randomly chooses a power between 1024 and 65,000 (65,536 to be exact) for the data.

My guess is...if you are able to connect and successfully authentication to an FTP server, but not get a directory listing or transfer files, there are two possible causes. First, you are using passive FTP and 1024-65536 are not open through your firewall. Second, your firewall only has port 21 open and not 20 _OR_ 1024-65536.

If you have a statefull packet filtering fw, you should be able to create a rule that will allow outbound connections to 1024-65536 when you successfully connect to that same IP on port 21. Generally, it's better to just open 20/21 and use normal FTP.

- G!mpy

Quote:


	Originally posted by mehronx I'm behind a router with Network Address Translation I believe it is called. So my client and my system config should be under Passive mode? What is Passive mode by the way?

mehronx · 05-14-2003, 01:25 PM

I had to start FTP in my system Firewall.

I didn't realize that I had to start FTP to connect to other ftp hosts. I was under the assumption that it was only for incomming connections.

However, I guess I still block incomming connections through my router so I'm all good.

Thanks.

05-14-2003, 11:06 AM	#1
mehronx Triple-A Player Join Date: Apr 2003 Posts: 86	No FTP client working under OSX I've been having an issue where I cannot connect to FTP servers under OS X. Whether I use the terminal ftp client, Transmit, or Fetch, the client hangs after connecting while "Receiving file list". I've tried both passive and non passive mode with no luck. I believe that if I let the client continue to try, I get "Data connection could not be made."

05-14-2003, 11:18 AM	#3
mehronx Triple-A Player Join Date: Apr 2003 Posts: 86	Passive vs. Non Passive I'm behind a router with Network Address Translation I believe it is called. So my client and my system config should be under Passive mode? What is Passive mode by the way?

05-14-2003, 01:25 PM	#5
mehronx Triple-A Player Join Date: Apr 2003 Posts: 86	Got it! I had to start FTP in my system Firewall. I didn't realize that I had to start FTP to connect to other ftp hosts. I was under the assumption that it was only for incomming connections. However, I guess I still block incomming connections through my router so I'm all good. Thanks.

05-14-2003, 11:12 AM	#2
Mikey-San Hall of Famer Join Date: Jan 2002 Posts: 3,541	I know you've mentioned passive vs non-passive, but did you set that in the FTP app or in the OS X system prefs? (If you're behind a firewall, you'll need to use PASV mode to use FTP.)