Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Eski

macrumors newbie
Original poster
Oct 15, 2007
16
0
Hi folks, first post so hope you don't me asking this on the web design forum but I guess you guys will be the real experts using FTP all the time.

I have a server setup that I (and all my web design students) have been FTP'ing into for some years. I've always done this with WSFTP on a PC, IP address, ID, Password, Port 21 and uncheck passive (as the server doesn't want this).

However, since moving to a mac this has become a problem. It will let me connect, but won't display the files in the remote folder, and won't let me upload. Is this common, is there a quick fix?

Cheers
 
The Finder doesn't allow for anything other than Read-Only.

You need to use a 3rd party FTP client.

My personal favorite is Transmit.
 
tried them

Tried them all, same problem.

In fact just installed FireFTP on Firefox on a PC and it works fine. It must be something on the Mac or something on the server that doesn't like the Mac.

Cheers
 
Fetch. It's really handy to do CMD-B while in a Fetch window and a browser pops up, browsing whatever you had selected in that window.
 
Mac OS X ships with the "standard" FTP client called "ftp".

Yes you can find another if you like but you don't "need" a 3rd party client. The advantage of using "ftp" is that it is the reference and is certain to work with with all FTP servers

Sigh.

And what percentage of people want to use the command line to FTP?

I think a significant portion of Mac OS X user know nothing about command line and prefer to keep it that way. Those users need a 3rd party client.
 
Why should it be router? PC going through same router (with passive unchecked) works fine.

Ps. I don't kneed to know which client folks, I'm after finding what in OSX is causing the problem. Cheers.
 
Transmit has integration into Textmate and other applications. It gets my primary vote with a secondary vote going toward Fetch.
 
Why should it be router? PC going through same router (with passive unchecked) works fine.

Ps. I don't kneed to know which client folks, I'm after finding what in OSX is causing the problem. Cheers.

So did you try it?

There is no reason why OSX would not let you FTP. It's either a.) you, b.) your router.
 
Why should it be router? PC going through same router (with passive unchecked) works fine.

Ps. I don't kneed to know which client folks, I'm after finding what in OSX is causing the problem. Cheers.

blocked by firewall?

system preferences -> sharing -> firewall -> ftp access.
 
Perhaps there are some errors going on in the background with the connection. Right after doing a connection open up Console (/Applications/Utilities/Console) and see if there are any errors relating to the program you're using. You can also see if the program you're using has any type of log file that may give some clues as to what is going on.

If you're familiar with using ftp from the command line try doing that and see if you can at least see the files on the server. This is just a troubleshooting activity.

Also a screenshot of this may be helpful, from whichever program. I personally use Fugu as my ftp program on Mac. Link for it is in an above post if you want to try it.
 
Try OneButton FTP

I use OneButton FTP. It's easy to use, gives you a nice gui that display files on both the remote server and on your 'desktop'. I own a publishing company and recommend it to all my artist for when they transmit large files (200+ megs) to me.

The FTP client built into OS X is functional (sometimes) but it doesn't play well with some servers

And it's free!
 
Resolved

:) solved.. moved to Leopard. Ftp now works fine.
 
I asked this very question a couple of months ago and someone suggested Transmit.

I have been using Transmit for the past couple of months and it is fantastic.

I too used to use WSFTP on the PC and find Transmit a breeze.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.