"ECONNREFUSED - Connection refused by server" and Dyndns

[bomberb17]

Hello, I'm running FileZilla server on a computer that has also Dyndns. Ports are properly forwarded in the router.
In the client side I'm using Filezilla client, I connect to the server and everything seems to run ok. But after some time while downloading, I get the message:
ECONNABORTED - Connection aborted
and then when the client tries to reconnect I get the message
ECONNREFUSED - Connection refused by server
Only if I reset the server's router, I can connect again.
After looking at some posts in this forum, I found out that I have to select this option



but if I do this, then each time I try to connect to the sever, the router resets!!!
Again, I'm running Dyndns on server side and I'm using the dns name in the client side to connect to the router.
Any help?

[boco]

Only if I reset the server's router, I can connect again.

but if I do this, then each time I try to connect to the sever, the router resets!!!

Any help?

That router is faulty and needs to be replaced (or at least its firmware updated).

[bomberb17]

No the router is ok, works with everything else fine, I use it for video streaming, gaming, etc. no problems at all.

[botg]

but if I do this, then each time I try to connect to the sever, the router resets!!!

No the router is ok, works with everything else fine, I use it for video streaming, gaming, etc. no problems at all.

You are contradicting yourself. How can the router be both fine and at the same time resetting itself constantly?

[bomberb17]

I don't mean that the router resets randomly with no reason (which would indicate a faulty router). The router ONLY resets when I use the option in my 1st post and then I try to connect to the FTP server. If I use Filezilla's default option, FTP server works fine for a few hours until it disconnects the client and the "ECONNREFUSED - Connection refused by server" reply comes up.

[boco]

I don't mean that the router resets randomly with no reason (which would indicate a faulty router).

But exactly that's what it is doing. It resets when it has no reason to do so. You don't think that's a fault?