Your best friend for file transfer.

Fetch application logoFetch

getting message: ftp_list: 1,61 (state == GETTING_LIST) (2 posts)

  • Started 5 years ago by William
  • Latest reply 5 years ago from Jim Matthews
  • William Member

    i would like to work with fetch 5.5.3

    1: i work with a mac pro (osx 10.6.2) /synology ds409 server/ avm wireless router
    2: i can make a save connection to my server over port 989 / Type of connection is
    FTP-TLS/SLL. (synology dosen‘t support sftp).

    what‘s happen: It works well but i can see my list of contents!

    see the following messages:

    Fetch 5.5.3 (5E778) Intel running on Mac OS X 10.6.2 (10C540) Intel German
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH55001-23ZA-YCCM T
    Connecting to port 989 (Mac OS X firewall is allowing connections) (26.03.10 09:24)
    Connected to port 989 (26.03.10 09:24)
    220 DiskStation409 FTP server ready.
    234 AUTH SSL command successful.
    USER admin
    331 Password required for admin.
    230 User admin logged in.
    PBSZ 0
    200 PBSZ command successful (PBSZ=0).
    PROT P
    200 Protection level set to Private.
    215 UNIX Type: L8
    257 "/" is current directory.
    500 MACB ENABLE: command not understood.
    CWD /
    250 CWD command successful.
    257 "/" is current directory.
    TYPE A
    200 Type set to A.
    227 Entering Passive Mode (81,221,216,82,217,57)
    Making data connection to port 55609
    ftp_setup_dataconn() passive mode dataconn failed, result = 1,61
    PORT 192,168,178,24,203,19
    500 Illegal PORT range rejected.
    ftp_list: 1,61 (state == GETTING_LIST)

    i dont now what‘s going wrong, mayby you can help me?
    thank you

    Posted 5 years ago #

  • Jim Matthews Administrator


    Unfortunately this setup won't work; you can't do secure FTP (aka FTPS, or FTP with TLS/SSL) to a server that is behind a Network Address Translation (NAT) router that is sharing a bunch of IP addresses. The problem is that the NAT device needs to make some changes to the FTP PORT and PASV commands as they go by, but if the connection is encrypted it can't do that.

    Your options are:

    1) Get a NAS server that supports SFTP
    2) Put the NAS directly on the Internet with a dedicated public IP address, not behind a NAT device
    3) Use regular (non-encrypted) FTP


    Jim Matthews
    Fetch Softworks

    Posted 5 years ago #


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