NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
FTP configuration
Hi,
Extremem frustration here. :( I am trying to transfer some files from my website via ftp and cannot get it to connect via Filezilla. I'm not very technicial and have done what I can. Attached is the error I got. Since the IP was wrong, I tried to manually put it in. No dice.
I went to my settings, and the Proxies for the router, but I have no idea what to put in the server and port. Would that be the soution?
Any suggestions? Truly appreciate it!
Lisa
> Command: PASS ***********
> Error: Connection timed out after 20 seconds of inactivity
Hmmm. That's in passive mode (Settings > Connection > FTP :
Transfer Mode)?
My FTP experience is almost exclusively with old/insecure FTP, not
this fancy new stuff with TLS, so I know nothing, but it's clear that
communication up through the initial handshaking is working, and then it
goes bad after you get authenticated. (Presumably, you'd get an error
message if you put in a bad password, which might be interesting.)
My expectations would be low, but you might try extending that
20-second timeout a little (60s?) to ensure that the server's not simply
too busy to respond promptly when it tries to locate your home directory
(which it should do after it accepts your credentials). (Settings >
Connection : Timeout)
4 Replies
> I went to my settings, and the Proxies for the router, but I have no
> idea what to put in the server and port. Would that be the soution?
I doubt it. Unless you have a good reason to deal with proxy
servers, you probably don't want to open that door. I'd start by
clearing any Proxies stuff which you might have tried to configure.
> I am trying to transfer some files from my website via ftp and cannot
> get it to connect via Filezilla.
"cannot get it to connect" is not a useful problem description. A
log transcript (the top pane) might be more helpful. (Check it for user
credentials or other private info before posting it here. Also,
copy+paste of the actual text would be better than a picture of the
actual text.)
If your primary concern is that "Wrong external IP address" complaint
from the "configuration wizard", then I'd ignore it, and see if you can
do any useful work with a real FTP server. I don't know what this
"wizard" is trying to do, but I've never noticed it before, and I've
never needed to do anything special to get FileZilla to work through any
of the (many) routers at the two different sites where I've used it.
Now that I know of its existence, I've found and tried Settings >
Connection > "Run configuration wizard now...", and selected all the
defaults. I got the same "Wrong external IP address" complaint, but
I've never had any trouble doing any actual work with FileZilla, despite
my "not correct" configuration.Thank you for your relpy. I made sure all of the log on information was correct. In addition, I contacted the host that I am trying to connect to, in order to transfer files and they were able to make the connection.
Thank you,
Lisa
Here is the log transcript:
Status: Resolving address of ****
Status: Connecting to *****
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Command: USER ****
Response: 331 User **** OK. Password required
Command: PASS ***********
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Waiting to retry...
Status: Resolving address of *****
Status: Connecting to *****
Status: Connection established, waiting for welcome message...
Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
Response: 220-You are user number 2 of 50 allowed.
Response: 220-Local time is now 10:31. Server port: 21.
Response: 220-This is a private system - No anonymous login
Response: 220-IPv6 connections are also welcome on this server.
Response: 220 You will be disconnected after 2 minutes of inactivity.
Command: AUTH TLS
Response: 234 AUTH TLS OK.
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Command: USER ******
Response: 331 User ***** OK. Password required
Command: PASS ***********
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Disconnected from server
Status: Resolving address of ******
Status: Connecting to *****
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Command: USER ******
Response: 331 User ****** OK. Password required
Command: PASS ***********
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Waiting to retry...
Status: Resolving address of *****
Status: Connecting to ******
Status: Connection established, waiting for welcome message...
Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
Response: 220-You are user number 2 of 50 allowed.
Response: 220-Local time is now 10:32. Server port: 21.
Response: 220-This is a private system - No anonymous login
Response: 220-IPv6 connections are also welcome on this server.
Response: 220 You will be disconnected after 2 minutes of inactivity.
Command: AUTH TLS
Response: 234 AUTH TLS OK.
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Command: USER *******
Response: 331 User ***** OK. Password required
Command: PASS ***********
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Disconnected from server
> Command: PASS ***********
> Error: Connection timed out after 20 seconds of inactivity
Hmmm. That's in passive mode (Settings > Connection > FTP :
Transfer Mode)?
My FTP experience is almost exclusively with old/insecure FTP, not
this fancy new stuff with TLS, so I know nothing, but it's clear that
communication up through the initial handshaking is working, and then it
goes bad after you get authenticated. (Presumably, you'd get an error
message if you put in a bad password, which might be interesting.)
My expectations would be low, but you might try extending that
20-second timeout a little (60s?) to ensure that the server's not simply
too busy to respond promptly when it tries to locate your home directory
(which it should do after it accepts your credentials). (Settings >
Connection : Timeout)