Having a nightmare trying to FTP photos overseas… Connections dropping out etc etc etc… Does anyone have any good ideas for other sending options other than FTP? I recently upgraded to the fastest broadband in Australia and I’m still having problems… Thanks in advance…
Which FTP program are you using? I just shifted to Filezilla www.filezilla-project.org and it has made a lot of difference to my overseas FTPing. The multiple simultaneous uploads speed things up and you can set it to reconnect if your connect to the host is lost…
Hi Damaso! I’m using Fetch… The little fetch dog running and running across the screen is driving me mad! I’ll look into Filezilla… Thanks for the tip!!
Back to original discussion…. Are there any alternatives to sending large files overseas besides FTP and dvd in a Fed-x packet (which can take 2 days+ from Australia with flight distances)... Just curious what other alternatives people are using for transferring/sending files… Thanks in advance
There are several protocol options when sending files over the internet – FTP, HTTP, as email attachments (not suitable for very large files), via instant messenger interfaces (AIM, ICQ etc.) and so on. But they all depend on a reasonably good connection. If your problem is your connection dropping, the transfer will be interrupted no matter what protocol you use.
I would recommend using an FTP client that allows you to resume interrupted transfers. I believe both Transmit and Captain FTP allow this…
Yousendit, Box.net and semdspace are all good you can also try using http://drive.heartinternet.co.uk which also alows you to move images around to others
The same problem applies to yousendit and you will have to start from scratch if the upload is interrupted. The plus side is that the file stays there and the client can download it whenever…
Personally I would choose ftp over anything else. It’s fastest option, with no extra overhead, and with any decent client you have resume option (most of today’s servers support resume anyway). For Mac Transmit is nice client, but personally I just send straight from Photo Mechanic. For PC, Total Commander is nice and easy one to use.
Just don’t go surfing LS when uploading and you should be fine.
FTP is best for “File Transport”, I don’t know about those websites as you still need to get them there. Clients servers would probably be less stressed then some file storage site. I run my own servers, a collocated one and sometimes one from home. Its nice to be out uploading something and to find it on your HDD when you get home.
There aren’t really any alternatives to FTP… there are fancy packages and some overheard protocols like sftp which is ftp over an encrypted tunnel but ftp is the standard. I suppose you could torrent your assignments… Its possible to setup private torrents but it might be a little strange getting the client to get it on the other end and they could only get it when you were online.
Sista T: I USE CYBER DUCK and i’ve never (ever) had a problem….any chance u’re sending to V??...if yes, that might be the problem (send me a PM and i’ll explain: i have experience with FTP problems with V)....
FTP is infact an outdated protocol, and a security risk. It was specified in the early seventies, and there are several better alternatives. It is indeed still widely used, but I don’t understand why, considering..
Your data and, more importantly, your password are sent unencrypted, any person who wants to check in on what you’re sending, and which password you have, can do so with a so called packet sniffer. FTP doesn’t transfer a file’s date and timestamp, which can be frustrating if you have a large archive you want to search by date. There’s more, just google it, but this is enough to stop using it I guess.
SFTP is not yet a standard, but it’s much safer, and cyberduck, transmit, etc. all support it. You could also use FTP with SSL if you can’t use SFTP..
SFTP is great, I have been using it for years with much success (before photography I was a computer nut and used openbsd for everything). Though sftp only works if the end server supports it.
I used winscp for windows, its free and does the job. Its built on top of putty a good ssh client. Though I doubt many of you have a need for that…
Thanks everyone for your very helpful tips/links and insight… I sent successfully last night via FTP (Filezilla) and www.yousendit.com ... Thanks Jethro for the moving video of the postman in the hills of Kentucky hand delivering mail. It reminded me of a past life when in lived in the US. During the last few days of frustrating FTP”ing”, I had a vision of tying a dvd to the leg of a pigeon and pointing them toward Europe and yelling “Fly like the wind”. The carrier pigeon would have arrived before my broken FTP connections… Thanks to LS, I won’t need to resort to animals hand-carrying my files to far-flung lands…
Phil theoretically you are right, but in practice it’s really not like this. First of all, there’s way too much traffic floating around that chances, someone will be sniffing your traffic are quite small. Second, it’s still just photos, not some highly classified documents, which gets transfered, ok username and password are also sent on begining, so this is still problem. If someone is really paranoid about this, I still suggest ftp, but through secure VPN IPSec tunnel.
I had similar nightmares with FTP and macs – tried a dozen different programs, fiddled with all their settings and contemplated a career change until I realized the problem was my mac was going to sleep before the transmission was complete, bedding the FTP programs with it. Now the bugger never gets to nap and I’ve haven’t had a single drop out since.
Also, I switched from fetch to captain FTP – seems more robust, versatile and instead of stupid mangy running dogs has pirate themes.
Tamara – and others – FTP is still the best system out there for filing your pictures. I think if you’re having dramas, it’s not so much the FTP technology itself but problems with the implementation at either end.
I lobbied for years to get my work to set it up for us. They finally did it to shut me up. Now I don’t have to use silly systems like ZModem and web-based uploading, it makes a world of difference. I’ve filed from locations where you have only a smidgin of bandwidth – not even enough to load a webpage before the browser times out – but just enough to know you’re online. And here, FTP gets my pictures out. I was in a forrest in Belgium a few months ago, first tried filing via that web based system. Fifty minutes later, no joy, not one had moved. As soon as I switched to FTP – in the same conditions – pictures were moving at a rate of one every two or three minutes.
Wade… you’ re a angel of technology & I look forward to connecting one day into your base of knowledge and ideas… Any hints/tips are welcome as they are revelations from creative sources and tried and tested by your own hands… Thank you! I hope you are enjoying London and life in Europe (the old country vs. the new country here in Australia)!!! We miss you here in Sydney….
I stopped using a direct FTP connection with most of my clients and instead set up each one with a password protected gallery with direct downloads on Photoshelter. That way I can manage the uploads in batches if necessary, can confirm the files integrity and can even see which ones they used. Some still want me to direct FTP the files but they are few now. Heck, some of my clients don’t even have an FTP set up so the Photoshelter prevents me from having to burn a disc and FedEx it.
Jonathan – but how are you sending your pictures to PS? PS is a distribution platform.. you still need to find a way to move your stuff to it in the first place, right?
Daniel – I don’t know what you’re shooting mate, but I am fairly confident the CIA would prefer to spend their time water-boarding than to intercept, packet by packet, my file transmissions. :)
“any person who wants to check in on what you’re sending, and which password you have, can do so with a so called packet sniffer”
This is a huge overstatement. To do packet sniffing one needs to be able to get physical access to a wire on the route of the FTP packets. In practice this means that whoever wants to sniff the traffic needs to be able to listen on the uplink wire of your network, or the wire coming in or out of the relay routers in between your network and the destination network. There are still many people who can do that (the network administrators), but not “any person who wants”.
SFTP is a good option, but not all servers support it, and encrypting the data may mean additional overhead, i.e. you may end up transferring more data with SFTP than with FTP for the same file. For some applications, FTP is a reasonably good solution.
Depending on the layout of the network you are on and the end server on that may include a lot more people then just the admin.
There are other ways to intercept packets, and not to be a scare monger or anything but there are lots of people that aren’t supposed to have access to routers and gateways around the internet that do. Passwords sent in plain text are pretty easy to acquire if they really want them.
The thing keeping you safe is that they have very little reason to be interested in your ftp password.
If I need to use ftp I use passwords which I don’t use for anything else. SFTP does have an overhead but its not major, most of it processing power to encrypt/decrypt on the fly.
Arcady, please forgive the paranoia. :) But if you’re on the road, how likely is it to have access to a private wire? If some WLAN or public access is are all you have, I would never rely on FTP for sending more or less sensitive data, and I’d rather err on the side of caution than to hand over my user data. Cheers
My point was to address what I find is a common misconception that a random Joe Blow can easily sniff the stuff you send over the Internet. But, I agree, the chances to lose the FTP login and passwords are quite real, just not to “anyone who wants them”.
Those using FTP should at least make sure they are not using the same user name and password for other purposes (email and such).
one thing to check is if your ftp program is connecting using “passive” ftp or “active” ftp. Look for this option in whatever program you’re using and change it to the other to see if you notice a difference in behavior.
The reason for security concerns with FTP are more because of hackers forcing (packet overflows) the FTP servers and then being able to upload rootkits and take over that server to do with as they please.. I have not heard of anyone that has had their ftp upload/download sniffed and compromised. SFTP was a response to the vulnerability of FTP server applications and while better in keeping hackers off the servers it still can be forced. But SFTP has to be available as a protocol from receiving server, not always the case. Having a good client Fetch, Transmit, etc should mitigate active, passive, sftp, ftp as they attempt to connect at best quality session with destination server.
Dropping connections is a function more of line/signal quality than ftp clients or protocol. I would imagine that phone service from australia to europe or usa has 2 possible paths: satellite or undersea cable. Since FTP is a close to peer to peer connection any degradation of the signal or slowness of packets will cause drop connections or slow transfers. I am not sure changing ftp clients will affect that. Speed of connection at sending ending, speed of connection and quality of server at receiving end all factor in. For those interested a traceroute to the destination IP address will tell you how many hops (or routers) your transmission has to pass through. Since Tamara’s FTP was going to France, I would suspect the problem was within France Telecom which in my experience has always been less than reliable from south pacific to europe. (example: a pay phone in Tahiti calls Paris for directory/dialing information)
In addition if you attempt to send photos as photos: tif/jpeg they are NOT being send as a binary package. It is always better to zip an image as the zip process turns an image into a binary file which is much easier packets to send.