Your best friend for file transfer.

Fetch application logoFetch

Odd Fetch errors. (2 posts)

This is an archived topic. The information in it is likely to be out-of-date and no longer applicable to current versions of Fetch.
  • Started 22 years ago by Cardinal
  • Latest reply 22 years ago from Jim Matthews
  • Cardinal Member

    One of our clients is using Fetch 4.01 to upload files to our server (Windows 2000, running WarFTP for FTP services).

    The client says that he has experienced the same problems under Fetch 3.x, namely that file transfers timeout and hang Fetch. File size does not really seem to be the issue - the files he is transfering are usually 50k or less in size.

    We've adjusted the passive transfer settings (on and off), to no avail. Setting transfer type to raw data rather automatic seems to enable transfers, but very slowly (see the transcript below - client is connecting via single-channel ISDN and is getting speeds comparable to carrier pigeon).

    The client finally managed to garner a transcript, which is reproduced below:

    TYPE I
    200 Type set to I.
    PORT 192,168,1,61,124,238
    200 PORT command successful.
    STOR v62s27.pdf
    125 Ready to receive "v62s27.pdf" . Mode STREAM Type BINARY.
    226 Transfer complete. 50201 bytes in 77.33 sec. (0.634 Kb/s)
    Upload complete at 12|18|01 12:46:42 PM
    PORT 192,168,1,61,255,228
    200 PORT command successful.
    STOR v62s2701.pdf
    125 Ready to receive "v62s2701.pdf" . Mode STREAM Type BINARY.
    get_reply():con_conn->Getline() returns -3253

    Any help would be greatly appreciated. I'm at wit's end.

    PS: Other factors. Client is using a new G4 with factory-installed ethernet card and there is more than enough space on the server.

    Posted 22 years ago #

  • Jim Matthews Administrator

    Can the client upload any more quickly to another server, such as the incoming directory on (leave the User ID and Password fields blank)? Or has the client tried uploading to your server using a different FTP client? This sounds like a problem with the ISDN router.

    Jim Matthews
    Fetch Softworks

    Posted 22 years ago #

Topic closed

This topic has been closed.