Fetch and Crush FTP
aRKay
download from a Crush FTP (v5); however, I tired Transmit and
it downloads fine. What is really weird is I can upload using Fetch
but cannot download.
I am open for any suggestions Fetch settings I may need to change
to be able to download from a Crush 5 FTP site.
Jolly Roger
aRKay <ar...@nospam.qsl.net> wrote:
Have you checked the Fetch transcript window and the Crush FTP logs? If
so, what do you see?
--
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
aRKay
Jolly Roger <jolly...@pobox.com> wrote:
> In article <arkay-02B66B....@news.eternal-september.org>,
> aRKay <ar...@nospam.qsl.net> wrote:
>
> > For reasons I cannot explain I can no longer use Fetch (v5.5.3) to
> > download from a Crush FTP (v5); however, I tired Transmit and
> > it downloads fine. What is really weird is I can upload using Fetch
> > but cannot download.
> >
> > I am open for any suggestions Fetch settings I may need to change
> > to be able to download from a Crush 5 FTP site.
>
> Have you checked the Fetch transcript window and the Crush FTP logs? If
> so, what do you see?
I have and it looks like something is changing the ports for downloads.
I can connect to port 21 then the transfer changes to 2000 series. I am
not sure what's going on and neither is the owner of the crush site.
If you are interested I can mail you the transcrip off line.
Again no problems using Transmit. The problem with downloads from
the crush site is unique to Fetch.
Tom Stiller
aRKay <ar...@nospam.qsl.net> wrote:
> In article <jollyroger-DA498...@news.individual.net>,
> Jolly Roger <jolly...@pobox.com> wrote:
>
> > In article <arkay-02B66B....@news.eternal-september.org>,
> > aRKay <ar...@nospam.qsl.net> wrote:
> >
> > > For reasons I cannot explain I can no longer use Fetch (v5.5.3) to
> > > download from a Crush FTP (v5); however, I tired Transmit and
> > > it downloads fine. What is really weird is I can upload using Fetch
> > > but cannot download.
> > >
> > > I am open for any suggestions Fetch settings I may need to change
> > > to be able to download from a Crush 5 FTP site.
> >
> > Have you checked the Fetch transcript window and the Crush FTP logs? If
> > so, what do you see?
>
> I have and it looks like something is changing the ports for downloads.
> I can connect to port 21 then the transfer changes to 2000 series. I am
> not sure what's going on and neither is the owner of the crush site.
Isn't that standard for fTP transfers? Port 21 is only used for the
initial contact and the server directs the client to use a different
port for the actual transmission, freeing port 21 up for additional
connect requests.
>
> If you are interested I can mail you the transcrip off line.
>
> Again no problems using Transmit. The problem with downloads from
> the crush site is unique to Fetch.
--
Tom Stiller
PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3 7BDA 71ED 6496 99C0 C7CF
aRKay
Tom Stiller <tom_s...@yahoo.com> wrote:
> > I have and it looks like something is changing the ports for downloads.
> > I can connect to port 21 then the transfer changes to 2000 series. I am
> > not sure what's going on and neither is the owner of the crush site.
>
> Isn't that standard for fTP transfers? Port 21 is only used for the
> initial contact and the server directs the client to use a different
> port for the actual transmission, freeing port 21 up for additional
> connect requests.
Tom, you may be correct. I sure would like to know why Fetch cannot
download. This is an example of it crapping out on small .jpg file.
I have tried checking and unchecking the Fetch Passive preference setting
and it makes no difference.
TYPE I
200 Command ok : Binary type selected.
MACB ENABLE
200 MacBinary mode is now enabled.
SIZE AD4PU.jpg
213 131088
MDTM AD4PU.jpg
213 20090615184422
PASV
227 Entering Passive Mode (71,238,XXX,97,7,215)
Making data connection to 71.238.XXX.97 port 2007
RETR AD4PU.jpg
Download of AD4PU.jpg stalled with 0 bytes transferred (state ==
RGET_RETRIEVING)
Unsuccessful transfer of AD4PU.jpg (0/131,088 bytes, 0 bytes/sec, 0:30
elapsed) stopped at 12/10/09 1:06 PM (error: 2,-30036)
ftp_retrieve: 2,-30036 (state == RGET_RETRIEVING)
Tom Stiller
aRKay <ar...@nospam.qsl.net> wrote:
I dunno. My _guess_ is that either the server doesn't have read access
to the file or the client doesn't have write access to the target
directory.
Jolly Roger
That's an interesting error there. Have you sent this transcript to
Fetch Softworks for assistance with it?
aRKay
Tom Stiller <tom_s...@yahoo.com> wrote:
I checked the Fetch discussion board and it looks like I am not alone
with the state == RGET_RETRIEVING error message.
aRKay
Jolly Roger <jolly...@pobox.com> wrote:
Yes, and I noticed others are reporting the same (state ==
RGET_RETRIEVING) error and Fetch has not commented. Until fixed
I will use Transmit that works. What is really weird is Fetch still
downloads from other sites.
Warren Oates
aRKay <ar...@nospam.qsl.net> wrote:
> Yes, and I noticed others are reporting the same (state ==
> RGET_RETRIEVING) error and Fetch has not commented. Until fixed
> I will use Transmit that works. What is really weird is Fetch still
> downloads from other sites.
I gave up on those GUI apps when OS X came along. Now I use ncftp from
the terminal. Great program. Yes, of course it transfers whole
directories.
http://www.ncftp.com/
--
Very old woody beets will never cook tender.
-- Fannie Farmer
aRKay
Thanks to all that responded. I got in touch with Fetch and the
problem is FIXED. The fix was:
-----
And could you please try the following?
- Close any open connection to the server.
- Go the Fetch menu, and choose Preferences.
- Click the Obscure tab.
- Check the "Do not send MACB probe" checkbox.
- Connect to the server again.
- Try downloading.
Fetch Softworks
------
I have no idea what it means to "Do not send MACB probe"
but it worked and Fetch 5.5.3 is working great
Richard Maine
....
> - Go the Fetch menu, and choose Preferences.
> - Click the Obscure tab.
> - Check the "Do not send MACB probe" checkbox.
....
> I have no idea what it means to "Do not send MACB probe"
> but it worked and Fetch 5.5.3 is working great
I've never heard of that either.
At least it is in an appropriately named tab. :-)
Glad it is now working. Extra glad as I also have fetch. I don't find
myself using it a lot any more, mostly because I'm not ftping a lot any
more. But glad to know that their support is still alive and responsive
in case I need it.
--
Richard Maine | Good judgment comes from experience;
email: last name at domain . net | experience comes from bad judgment.
domain: summertriangle | -- Mark Twain
Tom Stiller
aRKay <ar...@nospam.qsl.net> wrote:
A little searching onGoogle shows:
The MACB command is sent to�find out if the server supports the
MacBinary encoding�format.� If it does, then transfers would be made
using�the MacBinary format instead of regular binary format.��
Jolly Roger
So the Crush FTP server doesn't support the MACB command. That would
likely make me think twice about using Crush as a server.
Have you ever considered a robust FTP server such as ProFTPd?
aRKay
Jolly Roger <jolly...@pobox.com> wrote:
The Crush FTP is not my server. It works great. I am not sure who
change what. Fetch worked with Crush then Crush went to V5
and Fetch went to 5.5.3 and that's when the downloads stopped.
The Crush owner is talking to the developer about the MACB thing.
David Empson
The "MACB probe" is the command to tell the server to enable MacBinary
support.
According to the transcript you posted earlier, CrushFTP accepted that
command:
TYPE I
200 Command ok : Binary type selected.
MACB ENABLE
200 MacBinary mode is now enabled.
...
This suggests that CrushFTP has a bug in its support for MacBinary,
causing downloads to fail if that command was sent.
--
David Empson
dem...@actrix.gen.nz