Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
FTP File Transfer Issues
521 views
Skip to first unread message
pixel_a_ted
Dec 26, 2012, 12:43:58 PM12/26/12
to
I have an early 2011 MacBook Pro, running 10.8.2, connected to the internet with an Airport Extreme Basestation. I wanted to submit some photos to an online print lab and have been unable to use FTP. In earlier OS versions, I was able to use Cyberduck without any problems. That program does not seem to work with Mountain Lion.
First, I downloaded and installed FileZilla. I was able to connect to the lab's server and started the file transfers but kept getting error messages. They suggested I connect to the internet directly with an ethernet cable. I disabled WiFi, took ethernet out of the basestation (maybe that was not the right thing to do??) and found the same result.
Then I downloaded and installed Forklift from the App Store. Same result - I can connect to the lab's server but after trying for a while the transfer aborts.
The lab was not able to help me, just suggesting that there may be something in the Mac that is blocking the transfer.
Any suggestions would be appreciated. Thanks.
First, I downloaded and installed FileZilla. I was able to connect to the lab's server and started the file transfers but kept getting error messages. They suggested I connect to the internet directly with an ethernet cable. I disabled WiFi, took ethernet out of the basestation (maybe that was not the right thing to do??) and found the same result.
Then I downloaded and installed Forklift from the App Store. Same result - I can connect to the lab's server but after trying for a while the transfer aborts.
The lab was not able to help me, just suggesting that there may be something in the Mac that is blocking the transfer.
Any suggestions would be appreciated. Thanks.
Message has been deleted
pixel_a_ted
Dec 26, 2012, 2:06:29 PM12/26/12
to
> Have you tried uploading the files to some other FTP server? If you can, the problem is probably not at your end.
Don't know of any other sites. Is there a public one I can use as a test?
> You may also want to try Fetch or Transmit.
Thanks, but I already tried two ftp programs, one of which I paid for, so I think the issue is not specific to any program.
pixel_a_ted
Dec 26, 2012, 3:01:47 PM12/26/12
to
Okay, found that FileZilla has an ftp site that you can use for testing. I connected to it okay but could not upload a small .txt file.
I have a feeling it's a simple setting somewhere at my end, but I haven't a clue what it is.
I have a feeling it's a simple setting somewhere at my end, but I haven't a clue what it is.
nospam
Dec 26, 2012, 3:06:13 PM12/26/12
to
In article <5ec75c97-c101-45c2...@googlegroups.com>,
pixel_a_ted <pixel...@yahoo.com> wrote:
> Okay, found that FileZilla has an ftp site that you can use for testing. I
> connected to it okay but could not upload a small .txt file.
do they allow uploads?
> Okay, found that FileZilla has an ftp site that you can use for testing. I
> connected to it okay but could not upload a small .txt file.
Jolly Roger
Dec 26, 2012, 3:06:59 PM12/26/12
to
You keep saying things like "it doesn't work", but that's not very
helpful to us. What would be much more helpful is verbatim error
messages, screen shots, step-by-step procedures showing what you have
tried and the results you got from it - anything with details.
--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.
JR
Mike Dee
Dec 26, 2012, 3:32:36 PM12/26/12
to
In article <81bfe4bb-ec80-4632...@googlegroups.com>,
Your ftp client is not set to PASV mode?
<http://slacksite.com/other/ftp.html>
If it looks like its not going to work for you, can you send the photos
by an alternative route? e.g. upload to a file storage site, Dropbox,
Rapidshare etc and send the link to the photo lab?
Or move photos onto a USB stick and mail it to them the old-fashioned
way?
--
dee
Your ftp client is not set to PASV mode?
<http://slacksite.com/other/ftp.html>
If it looks like its not going to work for you, can you send the photos
by an alternative route? e.g. upload to a file storage site, Dropbox,
Rapidshare etc and send the link to the photo lab?
Or move photos onto a USB stick and mail it to them the old-fashioned
way?
--
dee
dorayme
Dec 26, 2012, 4:56:45 PM12/26/12
to
> I have an early 2011 MacBook Pro, running 10.8.2, connected to the internet
> with an Airport Extreme Basestation. I wanted to submit some photos to an
> online print lab and have been unable to use FTP. In earlier OS versions, I
> was able to use Cyberduck without any problems. That program does not seem to
> work with Mountain Lion.
>
You may be best to ask Cyberduck, have you a paid for copy, they are
> with an Airport Extreme Basestation. I wanted to submit some photos to an
> online print lab and have been unable to use FTP. In earlier OS versions, I
> was able to use Cyberduck without any problems. That program does not seem to
> work with Mountain Lion.
>
very helpful. What are your settings for Cyberduck? Look in
preferences in the program and see if you can spot anything odd, like
say, under General/Default protocol it probably should be FTP. But the
online print lab might be wanting different. Do they require a
password? There might be issues on this, you might have to ask them
about this.
Can you reveal the online lab's address here so folk can take a look?
--
dorayme
pixel_a_ted
Dec 26, 2012, 6:24:50 PM12/26/12
to
> You probably don't have permission to *upload* to their server. ; )
I connect with a username and password, so I should have permission. Also, the transfers start but don't complete.
> You keep saying things like "it doesn't work", but that's not very helpful to us. What would be much more helpful is verbatim error
Command: STOR Photo4.jpg
Error: Could not write to transfer socket: EPIPE - Local endpoint has been closed
Response: 552 transfer failed
Error: File transfer failed after transferring 262,144 bytes in 1 second
Status: Starting upload of /Users/MyName/Desktop/Photos/11 x 14/Photo4.jpg
Status: Retrieving directory listing...
Command: PASV
Response: 227 Entering Passive Mode (199,242,245,75,16,94).
Command: REST 0
Response: 350 setting restart marker to 0
Command: MLSD
Response: 150 Opening ASCII data connection for directory listing
Response: 226 transfer complete
Command: PASV
Response: 227 Entering Passive Mode (199,242,245,75,16,95).
Command: REST 1472832
Response: 350 setting restart marker to 1472832
Barry Margolin
Dec 26, 2012, 7:06:41 PM12/26/12
to
> I have an early 2011 MacBook Pro, running 10.8.2, connected to the internet
> with an Airport Extreme Basestation. I wanted to submit some photos to an
> online print lab and have been unable to use FTP. In earlier OS versions, I
> was able to use Cyberduck without any problems. That program does not seem to
> work with Mountain Lion.
Is there really a commercial service in this day and age that doesn't
> with an Airport Extreme Basestation. I wanted to submit some photos to an
> online print lab and have been unable to use FTP. In earlier OS versions, I
> was able to use Cyberduck without any problems. That program does not seem to
> work with Mountain Lion.
have an HTTP-based upload facility, and only supports FTP?
Have you tried using the "ftp" command from Terminal?
--
Barry Margolin, bar...@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
JF Mezei
Dec 26, 2012, 7:16:44 PM12/26/12
to
On 12-12-26 12:43, pixel_a_ted wrote:
> First, I downloaded and installed FileZilla. I was able to connect to the lab's server and started the file transfers but kept getting error messages. They suggested I connect to the internet directly with an ethernet cable. I disabled WiFi, took ethernet out of the basestation (maybe that was not the right thing to do??) and found the same result.
If you use the command line FTP on OS-X, you can try "set passive"
> First, I downloaded and installed FileZilla. I was able to connect to the lab's server and started the file transfers but kept getting error messages. They suggested I connect to the internet directly with an ethernet cable. I disabled WiFi, took ethernet out of the basestation (maybe that was not the right thing to do??) and found the same result.
FTP assumes bidirectional connectivity in a way that is broken by NAT.
When client wants to download from server, it tells server "call me at
a.b.c.d port xxx. But that io/port combo is not valid beyond the NAT
router which remaps IP and ports, so the server tries to connect to
a.b.c.d post xxx and that doesn't work.
With passive mode, it flips things around to enable FTP to work through
NAT at one end. (but not at both ends)
If you are using a GUI FTP application, look in the preferences or
connection setup to enabe passive mode.
pixel_a_ted
Dec 26, 2012, 7:17:54 PM12/26/12
to
Well, I just called the photo lab to give them the specific error messages. They told me to go ahead and try again and wouldn't you know, while I was on the phone with them all the images transferred.
They said my internet may have been flaky today and that could have interrupted the transfers before.
Something I learned - he said if the transfer gets interrupted, it should just pick up from where it left off when you try again. Previously, I had deleted the partially transferred folders on their site and started over.
So, thanks for all your help but it looks like there was nothing fundamentally wrong with the methodology.
They said my internet may have been flaky today and that could have interrupted the transfers before.
Something I learned - he said if the transfer gets interrupted, it should just pick up from where it left off when you try again. Previously, I had deleted the partially transferred folders on their site and started over.
So, thanks for all your help but it looks like there was nothing fundamentally wrong with the methodology.
Barry Margolin
Dec 26, 2012, 8:19:12 PM12/26/12
to
In article <50db936e$0$49806$c3e8da3$12bc...@news.astraweb.com>,
Any decent NAT router should translate the PORT command and open an
incoming port for it. This has been a well-known requirement of NAT for
ages.
However, passive mode simplifies lots of things, and I think most FTP
clients default to it these days. This might have lulled some NAT
implementors into thinking they can get away without the special FTP
handling.
incoming port for it. This has been a well-known requirement of NAT for
ages.
However, passive mode simplifies lots of things, and I think most FTP
clients default to it these days. This might have lulled some NAT
implementors into thinking they can get away without the special FTP
handling.
Jolly Roger
Dec 26, 2012, 9:43:23 PM12/26/12
to
In article <b3851505-ef25-4d34...@googlegroups.com>,
See the "Response: 552 transfer failed" error? If you search the web for
FTP error code 552, you'll see the error code indicates that the storage
volume is out of free space. So your transfer could not complete because
there is no space on the destination to store the file you are uploading.
FTP error code 552, you'll see the error code indicates that the storage
volume is out of free space. So your transfer could not complete because
there is no space on the destination to store the file you are uploading.
Jolly Roger
Dec 26, 2012, 9:44:05 PM12/26/12
to
Message has been deleted
Paul Sture
Dec 28, 2012, 10:03:13 AM12/28/12
to
ISP?
The reason I ask is that I was trying to set up Filezilla on a friend's
computer a couple of weeks ago but had no success. In the end I
discovered that the router had a menu of security settings from "high"
to "low" security, and by default FTP was blocked. This was a router
supplied by his ISP and they had applied their own customisation.
--
Paul Sture
pixel_a_ted
Dec 29, 2012, 1:12:46 PM12/29/12
to
Paul Sture: I am using the Apple Airport Extreme Basestation. I really don't know enough about these things to provide any more information. The transfer finally worked with Filezilla, without any changes on my part from the time that it didn't work.
Jolly Roger
Dec 29, 2012, 1:32:30 PM12/29/12
to
In article <bc8b0837-a4ba-4cfb...@googlegroups.com>,
We've already established that the FTP failure was due to insufficient
free space on the server.
free space on the server.
Paul Sture
Dec 30, 2012, 3:59:23 AM12/30/12
to
--
Paul Sture
0 new messages