Your best friend for file transfer.

Fetch application logoFetch

connected, but no file transfer (5 posts)

  • Started 18 years ago by davidstock
  • Latest reply 18 years ago from davidstock
  • davidstock Member

    hi. i'm trying out fetch in OS 10.2, and have struggled for three days to upload some TIFF files to an FTP server. when i look at the transcript window, it shows me connecting and logging in successfully. however when fetch goes to get a list of files, it quits.
    then if i use the "put" command, i am logged in and taken to the correct directory on the server. but as soon as the first file starts to be stored, i get "ABOR" followed by a time-out error message. i've tried all the settings i can think of, including active/passive. can you help? thanks

    Posted 18 years ago #

  • Scott McGuire Administrator

    Hi,

    When you say "When Fetch goes to get a list of files, it quits" do you mean the entire Fetch application closes down, or do you mean it doesn't get the file list?

    We'll need some more information to help analyze the problem. What version of Fetch are you using, and what version of Mac OS X 10.2?

    And could you post the contents of the transcript window here after you try to get the file list and put a file?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 18 years ago #

  • guest Registered Member

    Thanks for your reply, Scott.

    Actually, I am using OS X 10.3.9 and Fetch 5.0.4. Fetch does not quit, it gives me a timeout message. Here is a typical transcript; trying to get a file list and then put a file:

    Fetch 5.0.4 (5A785) running on Mac OS X 10.3.9 (7W98) English
    StuffIt Engine 0x811, StuffIt SDK Version 9.0.1
    Expires 10/26/2005 T
    Connecting to ftp.yours.pl port 21 (10/14/05 2:24:56 PM)
    Connected to 195.94.216.108 port 21 (10/14/05 2:24:56 PM)
    220 ProFTPD 1.2.7 Server (ftp.yours.pl) [leeloo.photography.pl]
    USER redakcja
    331 Password required for redakcja.
    PASS
    230 User redakcja logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/storage/home/redakcja" is current directory.
    PWD
    257 "/storage/home/redakcja" is current directory.
    TYPE A
    200 Type set to A.
    PASV
    227 Entering Passive Mode (195,94,216,108,147,177).
    ABOR
    ftp_list: -30027 (state == GETTING_LIST)
    QUIT
    send_cmd():con_conn->Putline() returns -3208

    Update check skipped at 10/14/2005 02:26 PM (next check after 10/17/2005 07:28 PM)

    Connecting to ftp.yours.pl port 21 (10/14/05 2:26:54 PM)
    Connected to 195.94.216.108 port 21 (10/14/05 2:26:54 PM)
    220 ProFTPD 1.2.7 Server (ftp.yours.pl) [leeloo.photography.pl]
    USER redakcja
    331 Password required for redakcja.
    PASS
    230 User redakcja logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/storage/home/redakcja" is current directory.
    CWD /storage/home/redakcja/
    250 CWD command successful.
    PWD
    257 "/storage/home/redakcja" is current directory.
    CWD davidstock
    250 CWD command successful.
    PWD
    257 "/storage/home/redakcja/davidstock" is current directory.
    TYPE I
    200 Type set to I.
    PORT 192,168,0,100,192,161
    200 PORT command successful
    STOR commodity.tif
    ABOR
    ftp_store_setup: -30028 (state == RPUT_SETTING_UP)

    Thank you!

    Posted 18 years ago #

  • Jim Matthews Administrator

    Make sure that your OS X firewall is turned off. To check that, choose "System Preferences..." from the Apple menu, and click the Sharing icon, then the Firewall tab. If the firewall is running click the Stop button and then try Fetch again. If it still does not work please post the transcript.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 18 years ago #

  • davidstock Member

    Scott, it appears that the problem was with the server's firewal, not mine. Several large files have now transferred without a problem. Thanks for your help.

    --David

    Posted 18 years ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.