NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
FTP Error
Hi,
I have issue in connecting NAS with FTP using file zilla, shows below error while connecting
Status: Server sent passive reply with unroutable address. Using server address instead.
Command: MLSD
All required ports opened, from lan it is working good but using external ip throws error
Thirutender wrote:
No, it is not connecting but give error "Error: The data connection could not be established: ECONNREFUSED - Connection refused by server"
That status message isn't the reason for the failed connection.
Did you limit the passive port range in the NAS, and forward the full passive port range in the router?
Also, are your passive ports in the dynamic/private port range (49152-65535)? Ports outside that range will generally work, but it's best to use ports in the range that is reserved for private use. You definitely don't want to use ports < 1024 for this, as that can conflict with other services.
Note you can confirm that the passive ports are open for TCP using canyouseeme.org on your home network.
4 Replies
Replies have been turned off for this discussion
That is a normal status - not an error - and you should be able to access the shares anyway. Is that the case?
It's actually telling you that it is triggering a FileZilla feature (which is to substitute the WAN ip address for the signaled local LAN ip address when making the data connection back to the NAS). You can eliminate the status message by configuring masquerading in the ReadyNAS FTP server - but if you do that you will most likely lose local FTP access. So it's best to just ignore it.
No, it is not connecting but give error "Error: The data connection could not be established: ECONNREFUSED - Connection refused by server"
Thirutender wrote:
No, it is not connecting but give error "Error: The data connection could not be established: ECONNREFUSED - Connection refused by server"
That status message isn't the reason for the failed connection.
Did you limit the passive port range in the NAS, and forward the full passive port range in the router?
Also, are your passive ports in the dynamic/private port range (49152-65535)? Ports outside that range will generally work, but it's best to use ports in the range that is reserved for private use. You definitely don't want to use ports < 1024 for this, as that can conflict with other services.
Note you can confirm that the passive ports are open for TCP using canyouseeme.org on your home network.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
