[tellysurv]

Hi all,
First post in these forums so I apologize if this is the wrong forum to post in.

Here's my situation:

I've set up an FTP server using a Mac with PureFTPd server running as the server software. I have the software up and running as it should be and can connect with various FTP clients on different Windows XP machines with no problem.
However, when I try to connect to the server using other Macs running OS X, I can connect, but the directory will never get listed and will eventually time and and disconnect.
The only way that I can get it to connect is to turn off the firewall on the Mac machine. (I have tried to connect using "GO"--> connect to server menu as well as a client called "Cyberduck")

I am also using a dyndns.org hostname due to a dynamic IP from our ISP. Not sure if that matters or not. (Like I said, I have no problems connecting on a Windows machine)

I want to be able to connect without having to jump through any extra hoops because I need to get our clients to start utilizing the FTP services and I'm afraid that if there's too many extra steps or too hard, that they will not use it.

I have searched high and low for an answer to this and so far have not come up with anything except for instructions on how to connect to an FTP server (which I already know how to do).

Does anyone have any ideas as to what could be causing my FTP to not connect or anyway to make the firewall accept connections to an FTP server?

Thanks for any info...

Chris

[chrismear]

Originally Posted by tellysurv 

I've set up an FTP server using a Mac with PureFTPd server running as the server software.
...
However, when I try to connect to the server using other Macs running OS X, I can connect, but the directory will never get listed and will eventually time and and disconnect.
The only way that I can get it to connect is to turn off the firewall on the Mac machine.

Do you mean you're turning off the firewall on the server Mac, or on the client Mac?

As long as you're alllowing connections on port 21 on the server Mac (i.e. 'FTP access' is ticked on the Firewall tab), there should be nothing else you have to do on the server side.

On the client side, however, you may have to enable 'Passive FTP'. During a regular ('active') FTP session, the server makes connections to the client in order to send data or directory listings. These connections can be blocked if your client machine is behind a router or has its firewall set up to block them.

The behaviour you describe (initial connection works fine, then can't download any directory listings or data) points strongly towards this diagnosis.

On the client Macs, try going into Network preferences, choose the adaptor you're connecting to the appropriate network/Internet with, then under the Proxies tab, tick "Use Passive FTP Mode (PASV)". See if that makes a difference.

[tellysurv]

Hi Chris,

I am having to turn the firewall off on the client side. The server side is working great.

Your analysis of the situation is correct about the client side. I think something is being blocked by the firewall.

I have tried connecting in both passive and active modes. I have tried ticking and unticking the "Use Passive FTP Mode (PASV)" under the proxies tab all with the same result.
It times out after the "List -a" command in the client.

Any other ideas? This is driving me crazy!

Thanks!
Chris

[tellysurv]

UPDATE:

I got it working. I turned on firewall logging on the client Mac and tried to connect to the server. The log said that TCP port 49222 was being blocked by the firewall.
So, I went into the Mac firewall settings and created a new range from 49000-49900 and named it FTP Access (Active) and turned it on.

I then went into the client software (cyberduck) preferences and set the connect mode to Active.

After that, I have been able to connect with no problems from Mac to Mac.

It's an active connection, but it works. I would still like to figure out why the passive FTP will not work.