Your best friend for file transfer.

Fetch application logoFetch

When connecting to Windows NT - 426 Data connection closed, transfer aborted. (3 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 13 years ago by SherryMC
  • Latest reply 13 years ago from SherryMC
  • SherryMC Member

    I have recently started to get this message - occasionally (but increasingly so) - when connecting to some NT web servers. If I refresh or drag a file enough times, it usually lets me in finally, but it's erratic. Any ideas? Below is the transcript from Fetch.

    250 Directory changed to /cards
    PWD
    257 "/cards" is current directory.
    PORT 65,207,19,34,147,39
    200 PORT Command successful.
    LIST
    150 Opening ASCII mode data connection for /bin/ls.
    ABOR
    426 Data connection closed, transfer aborted.
    500 'ÚABOR': command not understood.
    CWD /cards
    250 Directory changed to /cards
    PWD
    257 "/cards" is current directory.
    PORT 65,207,19,34,66,76
    200 PORT Command successful.
    LIST
    150 Opening ASCII mode data connection for /bin/ls.
    ABOR
    426 Data connection closed, transfer aborted.
    500 'ÚABOR': command not understood.
    CWD /cards
    250 Directory changed to /cards
    PWD
    257 "/cards" is current directory.
    PORT 65,207,19,34,155,233
    200 PORT Command successful.
    LIST
    150 Opening ASCII mode data connection for /bin/ls.
    ABOR
    426 Data connection closed, transfer aborted.
    500 'ÚABOR': command not understood.
    NOOP
    200 Command okay.
    CWD /cards
    250 Directory changed to /cards
    PWD
    257 "/cards" is current directory.
    PORT 65,207,19,34,236,196
    200 PORT Command successful.
    LIST
    150 Opening ASCII mode data connection for /bin/ls.
    ABOR
    426 Data connection closed, transfer aborted.
    500 'ÚABOR': command not understood.

    Thanks!
    Sherry

    Posted 13 years ago #

  • Jim Matthews Administrator

    I would recommend checking the "Use passive mode transfers (PASV)" box in the Firewall section of Preferences.

    Jim Matthews
    Fetch Softworks

    Posted 13 years ago #

  • SherryMC Member

    I have tried checking Passive Mode, but am still having the same issue...

    However, I was able to get to a PC today and try with WS_FTP - and am getting the same error/issue. So, I suspect it goes "deeper" than just FTPing client software. It must be something on the host end that had changed...maybe something with WinNT - like a Service Pack upgrade or host FTP software or something on that end???

    Thanks anyhow!
    Sherry

    Posted 13 years ago #

Topic closed

This topic has been closed.