SmartFTP is an FTP (File Transfer Protocol), FTPS, SFTP, WebDAV, Amazon S3, Backblaze B2, Google Drive, OneDrive, SSH, Terminal client. It allows you to transfer files between your local computer and a server on the Internet. An “FTP Client” is a program that moves files between your computer and the web server. The use of an FTP client that supports FTPES is required to connect to the YCCD Web Hosting Server. YCCD suggests that employees use the free FileZilla FTP Client. The FileZilla software is available for Microsoft Windows, Apple OSX, and Linux.
Download yosemite server backup ftp for free. System Utilities downloads - Yosemite Server Backup by Barracuda Networks, Inc. And many more programs are available for instant and free download. Vicomsoft FTP Client for Mac: Free Download - Pro-level FTP/SFTP client. Download the latest versions of the best Mac apps at MacUpdate PHFTP ( PHP FTP ) download SourceForge Vicomsoft FTP Client is a pro-level, full-featured, fast and reliable, easy-to-use FTP + SFTP + FTPS client for OS X.
| Click here to return to the 'Perform direct site-to-site FTP with any FTP client' hint |
Hi
I do like Fetch and use this functionality a lot. Actually though, if you watch the status bars carefully, it is actually DL'ing to temp files on your local machine and UL'ing them to the second host and then cleaning up behind itself. On a high speed connection, this gives the illusion that you're going host to host, and is certainly convenient, but it is just an illusion. This becomes very obvious when working via dial-up ;)
I don't think this is a Fetch thing, but suspect it is just the nature of FTP. I could be wrong, but would imagine that Transit is doing something similar.
salut,
While this will not actually deposit the file on your computer (depending on how Apple implemented Finder FTP), you are NOT doing direct FTP to FTP site transfers. That's a specific protocol known as FXP, which is generally not enabled on FTP servers (pureftpd.org had a good description of FXP, if I recall). The file is still being transferred to your computer, then out to the FTP site, using your bandwidth twice.
This wont do direct site-to-site, the OS X mounting of the ftp site will be copying to your machine before sending to the other
I'm watching the output of fs_usage right now, and it doesn't appear to copy the file to your machine first (no long instances of 'write' commands are being dumped). It appears that it's just taking information from one volume and sending it to the next. Remember that FTP servers, when mounted in the Finder, are mounted in /Volumes.
Are you guys saying that if I mount my FireWire drive and drag a bunch of stuff into the Transmit window, I'm copying that stuff over to my HD first? I don't think so, and it's essentially--to the Finder, anyway--the same thing.
EVEN IF it's just an illusion, isn't a mighty convenient way of doing things when you need to, without having extra things around.
But unless fs_usage is lying to me, it works as it appears.
Crap. Forgot to add this:
It appears to (and would thus suck for modem users) use your rig's bandwidth as an in-between. (Wanted to acknowledge that since it was pointed out.)
Still worth being able to do, though, since not all servers can do direct transfer to other servers. :-/
You won't see anything with fs_usage because the data isn't going to disk, it's going network->RAM->network.
By default Fetch's server-to-server transfers work this way as well, but you can choose 'Direct server-server transfers' in the Misc. section of Preferences to make the transfer go directly between the two servers. It won't work if the servers are configured to only accept transfers from the IP address of the logged-in client (which is why it's off by default), but if the servers allow 3rd party transfers it can be very handy (and fast).
Jim Matthews
Fetch Softworks
You can do this with the standard command-line FTP client.
RTFM ftp(1) and look for the proxy command.
The basic idea is:
You start FTP by itself. (i.e., ftp, not ftp hostname.)
You connect to the 'main' machine via
ftp>open primaryhost
You connect to the other machine via
ftp>proxy open otherhost
Once logged on to each host, you can do normal stuff - e.g., like
cd /some/path/on/primaryhost
proxy cd /some/path/on/otherhost
Once you're ready, do a proxy get filename (or proxy put filename, etc.)
Voila!
Oh, and you have to set Passive Mode (PASV) for this to work, obviously.

---
?>

i guess i jus don't understand the point of using transmit at all...why not just mount both drives in the finder and drag and drop?
seems like it saves time to me...
why not just mount both drives in the finder and drag and drop?Because the Finder still doesn't support FTP uploading. I honestly don't know what the reason for this missing link of usability is but Apple has a tech note on it here which makes it sound like it's not something that will change anytime soon.
From what I've read (by those who are using developer builds), FTP uploading finally works in Panther.
I don't doubt there will still be some servers it has trouble with, but for the most part, this sounds like good news to me. (I just hope it's true.)
Ftp Client Yosemite Valley
Free Ftp Client
Oops, sorry. Now I've read that it is indeed still 'broken' in Panther. Looks like it works for some very small minority of people, but most of the time you still can't upload.
Comments are closed.