NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FTP access "ECONNREFUSED"
I have setup ftp service on my readynas 102 (latest firmware).
I can log in with the created ftp user from the local network using the internal ip and is set to you port 5000 and everything is working correctly and as expected. I have a dyndns forward. When using the dyndns address to access the ftp server, the client connects, I have to enter user name and password, but then the connection fails with message "ECONNREFUSED".
The port is forwarded correctly in router (I have a readynas duo also connected with the ftp server running on port 21 and this is running fine with apparently same settings apart from the port number).
Any ideas?
I can log in with the created ftp user from the local network using the internal ip and is set to you port 5000 and everything is working correctly and as expected. I have a dyndns forward. When using the dyndns address to access the ftp server, the client connects, I have to enter user name and password, but then the connection fails with message "ECONNREFUSED".
The port is forwarded correctly in router (I have a readynas duo also connected with the ftp server running on port 21 and this is running fine with apparently same settings apart from the port number).
Any ideas?
6 Replies
Replies have been turned off for this discussion
- If you toggle PASSIVE mode in your FTP client, does it behave any different?
- Chirpa is indirectly pointing out that you need to forward the passive ports used by the NAS FTP server in your router.
Most people only need 3 or 4 passive ports, so you should also narrow the range being used in the RN102. - I have disabled passive in the client and I now get a different error message:
500 illegal port error
Thanks for your help - If I disable passive mode then that error goes away, however it is replced with the following error in the client:
500 illegal port command
The line above the error in the log shows:
Port 192.168.0.119,146,92
Thanks for help so far, much appreciated - Re-enable passive ports, and choose a small range for them in the NAS configuration. Perhaps use 50001-50004 for passive.
Then forward 50001-50004 in your router to the NAS.
With some clients you will also need to set the masquerade address on the NAS to be your public IP (e.g., your ddns name). If you need masquerade set, then you will always need to connect via the ddns name - even if you are on the local lan. Otherwise you will see more connection issues.
One reason I recommend the FileZilla client is that it works without the masquerade being set, which makes it easier. - Thank you so much.
Set the NAS passive port range to 10 slots, forwarded those in router, set the masquerade to my Dyndns name and now everything is working.
All the help much appreciated.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
