ECONNRESET error when trying to login

[dmartens]

Using client 3.1.5.1 and Filezilla server 0.9.29

I am unable to log in - I get the following error log when trying:

Status: Resolving address of ftp.hitcrs.com
Status: Connecting to 64.xxx.xxx.xx:21...
Status: Connection established, waiting for welcome message...
Response: 220 Welcome to CRS file services
Command: USER xxxxxx
Response: 331 Password required for xxxxxx
Command: PASS *******
Response: 230 Logged on
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Error: Could not read from socket: ECONNRESET - Connection reset by peer
Error: Disconnected from server
Error: Failed to retrieve directory listing

I've seen other people with the same error on the boards but no solution was given. I've verified the NAT settings on the server side following the Network Configuration guide. I've read that there were security errors in the Filezilla server in previous versions that would cause this, but supposedly this is supposed to be fixed with this latest build.

Any suggestions?

[botg]

Read the Network Configuration guide.

[dmartens]

I did follow that guide in setting up my server & router. I know that routing is working since I can use other clients to connect to the server without any issues.

I just ran the config wizard on the client and got the following response along with a message to submit a bug report:

Connecting to probe.filezilla-project.org
Response: 220 FZ router and firewall tester ready
USER FileZilla
Response: 331 Give any password.
PASS 3.1.5.1
Response: 230 logged on.
Checking for correct external IP address
Retrieving external IP address from http://ip.filezilla-project.org/ip.php
Checking for correct external IP address
IP 68.126.158.59 gi-bcg-bfi-fj
Response: 200 OK
PREP 50989
Response: 200 Using port 50989, data token 438681838
PORT 68,126,158,59,199,45
Response: 200 PORT command successful
LIST
Response: 150 opening data connection
Response: 503 Failure of data connection.
Server sent invalid reply.
Connection closed

[boco]

The connection test is checking Active (PORT) mode. I guess all other clients tested are using Passive (PASV) mode. You must either set up the client (!) for Active mode or keep using Passive.

[dmartens]

So that doesn't solve my original problem then. The client is set to use Passive mode & the log indicates that, but I still get the ECONNRESET error.

[boco]

Seems to be still blocked by a firewall. Win Firewall?

[dmartens]

So why do my other clients work, but not Filezilla? That tells me it is not a firewall issue, but something in Filezilla client that is broken.

[boco]

I beg to differ. Firewalls track every executable individually, so one with a correct rule may work, while the next won't. Especially if the firewall is tampering with your data, which has been confirmed for Windows firewall.

What happens if you completely disable any firewall in the system?

[dmartens]

I have disabled the firewall on the server completely with out any change. The client has no firewall running. I've tested several different clients now. All are successful except Filezilla.

[dmartens]

I found this rejected bug report that indicates the need to set the timeout on the server higher.

http://trac.filezilla-project.org/ticket/3709

I've tried increasing the timeouts to 2 hours and still get the same ECONNRESET error when receiving the directory listing. Again this is only Filezilla client that fails. All other clients I've tried are successful.

[twanb]

I found this rejected bug report that indicates the need to set the timeout on the server higher.

http://trac.filezilla-project.org/ticket/3709

I've tried increasing the timeouts to 2 hours and still get the same ECONNRESET error when receiving the directory listing. Again this is only Filezilla client that fails. All other clients I've tried are successful.

I get the same error-message with some of the servers I use.

[noussibeau]

I've exactly the same problem without any solution !!
I posted a query on that subject before seing that one.
The only difference (not a small one) is that each client I tried does the same.
If you got the solution please explain it!!

[twanb]

I've exactly the same problem without any solution !!
I posted a query on that subject before seing that one.
The only difference (not a small one) is that each client I tried does the same.
If you got the solution please explain it!!

Without any chagnes I made I can login perfectly again... how weird.

[noussibeau]

you are right, that's weird .. technologies are somewhere magic (probably black magic!), experts are totaly powerless ... so the only thing I can do is to wait for the sky help me!
Happy new year !!!

[dmartens]

I finally had a chance to get back to the clients office and troubleshoot my issues a bit.

It turns out that their Netgear Router was dropping the passive request packets on port 21, even though I had forwarded all port 21 traffic to the internal IP address. Very odd. I couldn't find any setting on the router that would correct the problem so I changed the server port 23, and all is well.