Your best friend for file transfer.

Fetch application logoFetch

Unable to get file list. (8 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 12 years ago by Harryjb
  • Latest reply 12 years ago from Jim Matthews
  • Harryjb Member

    Note: Contents of Transcript window are at end of message.

    I am a registered fetch user and will be glad to forward my registration # if you require it.

    I have an adsl connection from Bellsouth going into a linksys router.

    I am using fetch 4.0.2 which I downloaded today. But the problem occurred with version 4.0 as well.

    I have two Mac and two pc's on my home network. The macs are each running an interation of 9.x. The problem occurs on both macs and on the pc's using a pc ftp program. So the problem is not with fetch but I hope you can help me sort this out.

    My wife connects to work through vpn but the problem occurs whether or not she is connected.

    I run two web sites. One is on Bellsouth through which I get my adsl connection. I have no problems when I ftp to bellsouth.

    The second web site is on another server-Louisville telecom.

    When I first set up the site on Louisville Telecom I could connect to the server but could not get file lists. Then, one day, I was able to get the file lists. Support at Louisville Telecom did not know why this happened.

    After a month or so of being able to connect and get file list and upload and download to Louisville Telecom I can still connect, but can no longer get my file lists. There is no problem connecting to and getting file lists from the bellsouth server.

    Passive mode is on.

    From my pc I was able to successfully ping Louisville Telecom. However when they ran tracer software the trace stopped at bellsouth.

    Any help you can give me will be greatly appreciated.

    Here is the contents of the transcript window.

    Fetch 4.0.2 System 0x910 Serial FETCHFL001-AQFA-GX11 TR
    Connecting to pleiadestheatreco.org port 21 (6/3/02 12:14:42 PM)
    220 ProFTPD 1.2.2rc1 Server (ProFTPD) [192.168.40.15]
    ADAT
    500 ADAT not understood.
    USER pleiades
    331 Password required for pleiades.
    PASS
    230 User pleiades logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/web" is current directory.
    MACB ENABLE
    500 MACB not understood.
    CWD /users
    250 CWD command successful.
    PWD
    257 "/users" is current directory.
    CWD pleiades
    250 CWD command successful.
    PWD
    257 "/users/pleiades" is current directory.
    PASV
    227 Entering Passive Mode (192,168,40,15,8,55).
    LIST
    421 No Transfer Timeout (300 seconds): closing control connection.
    ftp_list: -30001 (state == GETTING_LIST)
    QUIT
    send_cmd():con_conn->Putline() returns -3155
    Connecting to pleiadestheatreco.org port 21 (6/3/02 12:21:54 PM)
    220 ProFTPD 1.2.2rc1 Server (ProFTPD) [192.168.40.15]
    ADAT
    500 ADAT not understood.
    USER pleiades
    331 Password required for pleiades.
    PASS
    230 User pleiades logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/web" is current directory.
    MACB ENABLE
    500 MACB not understood.
    PWD
    257 "/web" is current directory.
    CWD /users
    250 CWD command successful.
    PWD
    257 "/users" is current directory.
    PASV
    227 Entering Passive Mode (192,168,40,15,8,66).
    LIST
    ABOR
    CStreamOT::Read() OTRcv() returned -3208
    Connecting to pleiadestheatreco.org port 21 (6/3/02 12:28:09 PM)
    220 ProFTPD 1.2.2rc1 Server (ProFTPD) [192.168.40.15]
    ADAT
    500 ADAT not understood.
    USER pleiades
    331 Password required for pleiades.
    PASS
    230 User pleiades logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/web" is current directory.
    MACB ENABLE
    500 MACB not understood.
    PWD
    257 "/web" is current directory.
    PWD
    257 "/web" is current directory.
    PASV
    227 Entering Passive Mode (192,168,40,15,8,70).
    LIST
    421 No Transfer Timeout (300 seconds): closing control connection.
    ftp_list: -30001 (state == GETTING_LIST)
    QUIT
    send_cmd():con_conn->Putline() returns -3155

    Posted 12 years ago #

  • Jim Matthews Administrator

    You could try unchecking the "Use passive mode transfers (PASV)" box in the Firewall section of Preferences, but I'd be suprised if that worked. It looks like data connections from your Mac to the Louisville Telecom server are being blocked. My best guess would be that a firewall is blocking them, in your DSL modem, or linksys router, or at Bellsouth. In the transcript you sent Fetch was trying to connect to port numbers 2103, 2114 and 2118 at 192.168.40.15. You could ask Bellsouth if there's any reason why such connections should be blocked.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 12 years ago #

  • midigeek Member

    <<<you could try unchecking the "Use passive mode transfers (PASV)" box in the Firewall section of Preferences, but I'd be
    suprised if that worked. It looks like data connections from your Mac to the Louisville Telecom server are being blocked. My
    best guess would be that a firewall is blocking them, in your DSL modem, or linksys router, or at Bellsouth. In the transcript
    you sent Fetch was trying to connect to port numbers 2103, 2114 and 2118 at 192.168.40.15. You could ask Bellsouth if
    there's any reason why such connections should be blocked.>>>

    This seems to work for me. I was having the same problem with Fetch 4.0.x and Transmit 1.6. Fetch 3.0.3 works great. Do you need the other ports enable for Fetch 4.0.x? I only enabled 20-21 for ftp.

    thanks
    Mike Stokes

    Posted 12 years ago #

  • Harryjb Member

    Originally posted by midigeek:

    <<<you could try unchecking the "Use passive mode transfers (PASV)" box in the Firewall section of Preferences, but I'd be
    suprised if that worked. It looks like data connections from your Mac to the Louisville Telecom server are being blocked. My
    best guess would be that a firewall is blocking them, in your DSL modem, or linksys router, or at Bellsouth. In the transcript
    you sent Fetch was trying to connect to port numbers 2103, 2114 and 2118 at 192.168.40.15. You could ask Bellsouth if
    there's any reason why such connections should be blocked.>>>

    This seems to work for me. I was having the same problem with Fetch 4.0.x and Transmit 1.6. Fetch 3.0.3 works great. Do you need the other ports enable for Fetch 4.0.x? I only enabled 20-21 for ftp.

    thanks
    Mike Stokes

    I really don’t think the problem is with Fetch. I also have a pc and the pc ftp program also will not work.

    I think the issue is with the isp hosting the web site or with the settings in my linksys router (the linksys people were not very helpful) or with my isp. Or some combination of the above.

    I’m really looking for a linksys and fetch user who has run into this problem.

    Thanks.

    Posted 12 years ago #

  • rupy Member

    I got the same problem : impossible to get the files list... The only solution on the web site is to upgrade tu 4.0.2... but I already use it ! I tried on my local network or with modem connection but it is still the same problem. I unchecked passive mode in the firewall, it didn't change anything...

    Posted 12 years ago #

  • Jim Matthews Administrator

    Rupy:

    Could you post (or email to support@fetchsoftworks.com) a transcript of connection attempts with PASV turned on and off? I'll see what I can figure out.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 12 years ago #

  • midigeek Member

    <<<i got the same problem : impossible to get the files list... The only solution on the web site is to upgrade tu 4.0.2... but I already use it ! I tried on my local network or with modem connection but it is still the same problem. I unchecked passive mode in the firewall, it didn't change anything... >>>

    With the passive enabled in Fetch 4.0.x or Transmit 1.6 I get the error about getting the file list. With it turned off in both Fetch 4.0.x and Transmit 1.6 everything works again like Fetch 3.0.3.

    If these ports 2103, 2114 and 2118 are required for Fetch then users like myself need to know as I can enable them into the Linksys BEFSR41 router. I will probably try it just to see.

    MS

    Posted 12 years ago #

  • Jim Matthews Administrator

    When passive mode is turned off Fetch chooses ports to listen on randomly; so while 2103, 2114 and 2118 were the ports being used in the transcript you posted, the next time you ran Fetch they'd probably be different.

    Jim Matthews
    Fetch Softworks

    Posted 12 years ago #

Topic closed

This topic has been closed.