NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
stgeorge
May 04, 2017Guide
ftp refusing connections
Hey all- I'm curious what the most typical reason is for the standard ftp server loaded on these nas devices to 'refuse connections' ? Here's the messaging that I'm getting via a filezilla cl...
stgeorge
May 05, 2017Guide
I actually have had masquerading set on the NAS- that wasn't the issue- the issue was that the passive port range (in the ftp server's settings) was not the same range as that which I had forwarded in our router. It sounds pretty stupid of me, I'm sure, but the experience that I've found in the past (aka earlier versions of FileZilla) was that I didn't need to forward passive ports at all. In fact, if I remove the port forwarding instruction in my router for the passive port range, many ftp clients will work fine, and FileZilla used to, but this current version will not. Once I forwarded the same passive port range as was in the ftp server's settings, FileZilla works beautifully.
StephenB
May 05, 2017Guru - Experienced User
stgeorge wrote:
the experience that I've found in the past (aka earlier versions of FileZilla) was that I didn't need to forward passive ports at all.
It the port isn't forwarded by the router, the connection can't be made. The client behavior doesn't matter, there is no workaround that it can use.
Alternative explanation: Your old FTP server was using upnp to open the passive ports in your router.
stgeorge wrote:
I actually have had masquerading set on the NAS- that wasn't the issue
The status message in the first post says that either masquerading is mis-configured or it is not enabled. That might have changed after that post was made. So perhaps double-check that setting.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!