NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

PaulC_303's avatar
PaulC_303
Aspirant
Feb 08, 2016
Solved

Cannot connect to FTP server with C3700-100NA but CAN with WNR2000v4

Cannot connect to FTP server from one computer…. but can from another using same credentials.

Only difference between the two PC’s is they are on different routers in different locations, same ISP, same FileZilla version.

 

What could possibly be causing this behavior?

 

The Server is ProFTPd on an Ubuntu instance on AWS EC2 with Passive mode enabled.

 

Both PC’s are Windows 10

Router settings are virtually identical between the two.

 

PC 1 that can connect.

Router: Netgear WNR2000v4 (V1.0.0.60) with separate cable modem.

FileZilla log

Status:          Connecting to xx.xx.xx.150:21...

Status:          Connection established, waiting for welcome message...

Status:          Insecure server, it does not support FTP over TLS.

Status:          Server does not support non-ASCII characters.

Status:          Logged in

Status:          Retrieving directory listing...

Status:          Server sent passive reply with unroutable address. Using server address instead.

Status:          Directory listing of "/" successful

 

 

PC 2 that cannot connect

Router: C3700-100NAS (V2.02.06) modem/router combo

 

FileZilla log

Status:          Connecting to xx.xx.xx.150:21...

Status:          Connection established, waiting for welcome message...

Status:          Insecure server, it does not support FTP over TLS.

Status:          Server does not support non-ASCII characters.

Status:          Logged in

Status:          Retrieving directory listing...

Command: PWD

Response:  257 "/" is the current directory

Command: TYPE I

Response:  200 Type set to I

Command: PASV

Error:            Connection timed out after 20 seconds of inactivity

Error:            Failed to retrieve directory listing

 

 

Just FYI….

Filezilla log when connecting PC 2 to a windows ftp server.

Status:          Connecting to xx.xx.xx.180:21...

Status:          Connection established, waiting for welcome message...

Status:          Initializing TLS...

Status:          Verifying certificate...

Status:          TLS connection established.

Status:          Logged in

Status:          Retrieving directory listing...

Status:          Calculating timezone offset of server...

Status:          Timezone offset of server is -28800 seconds.

Status:          Directory listing of "/" successful

  • Here is what I found was the problem and how I fixed it.

     

    My FTP server is hosted on Amazon EC2 and set to use Passive mode. The server has a 'real' IP address, and a 'elastic' public IP address using NAT. It would appear that the C3700 has difficulty with the server responses and fails. The WNR2000 is smart enough to deal with the buggy response and succeeds.

     

    The fix was to add MasqueradeAddress [elastic public IP address] to the proftpd config, and all is well.

     

    http://www.proftpd.org/docs/howto/NAT.html

4 Replies

  • Can you try another service like ssh and see if that works or fails like the FTP? I have a C3000 that is doing the same thing. 

     

    Thank you 

    Dave

     

  • vkdelta's avatar
    vkdelta
    NETGEAR Employee Retired

    can you please check with PASSIVE mode disabled in the client and AWS on the PC having problem (looks like client config could be causing issue)?

     

    we will get this checked on our side as well. 

  • vkdelta's avatar
    vkdelta
    NETGEAR Employee Retired

    btw, thanks for bringing this to our attention and I appreciate the details you have provided.

  • Here is what I found was the problem and how I fixed it.

     

    My FTP server is hosted on Amazon EC2 and set to use Passive mode. The server has a 'real' IP address, and a 'elastic' public IP address using NAT. It would appear that the C3700 has difficulty with the server responses and fails. The WNR2000 is smart enough to deal with the buggy response and succeeds.

     

    The fix was to add MasqueradeAddress [elastic public IP address] to the proftpd config, and all is well.

     

    http://www.proftpd.org/docs/howto/NAT.html