NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
corkscrew22
Sep 12, 2021Aspirant
filezilla
I am trying to connect to my ReadyNAS Duo v1 with filezilla, see the attached screen shots. I am using the admin log in and password. It appears to be connecting ok but will not get a directory ...
- Sep 14, 2021
corkscrew22 wrote:
here are the ftp settings in screenshots below
This one needs to be set to passive, not active.
schumaku
Sep 13, 2021Guru - Experienced User
Looks like a connection attempt on the same local network and subnet.
If an ftp connection fails t this point is because of the data connection can't be established, either as an active connection, or as a passive connection. Have tried both? Possible cause could be an undefined firewall config on this Linux system for example.
If there are other routers or security appliances in the data path, again possibly a firewall issue. Reason: an FTP-ALG typically in place can't see and analyze the encrypted ftp-conrol connection. The FTP-data ports need to be allowed by the firewall, and NAT-forwarded in case there is NAT in place.
StephenB does the FTP TLS work on the legacy systems? Appears the ftp control connection can be established.
StephenB
Sep 13, 2021Guru - Experienced User
schumaku wrote:
StephenB does the FTP TLS work on the legacy systems?
Yes. You can't block unencrypted connections with the legacy NAS, but it will accepted encrypted ones.
schumaku wrote:
Looks like a connection attempt on the same local network and subnet.
...
Appears the ftp control connection can be established.
Agreed.
Looking more closely, the passive port command appears to be on IP 192.168.2.3, but the control connection appears to be on 192.168.2.9. That suggests that masquerading isn't set up correctly on the Duo.
corkscrew22: If you have masquerading set on the Duo's FTP settings, disable it. Some clients need it, but FileZilla isn't one of them.
- schumakuSep 13, 2021Guru - Experienced User
StephenB wrote:
Looking more closely, the passive port command appears to be on IP 192.168.2.3, but the control connection appears to be on 192.168.2.9. That suggests that masquerading isn't set up correctly on the Duo.
corkscrew22: If you have masquerading set on the Duo's FTP settings, disable it. Some clients need it, but FileZilla isn't one of them.
Valid observation.
On a side note (when I have it right the Duo has only one network adapter so this does not apply): There is a Kernel control that does enforce the TCP/IP stack to use the same interface for the return traffic. This is essential when there are multiple interfaces are connected to the same IP subnet - it can happen that the return traffic does go out over a different interface. This was fine as long as no stateful firewalls are in the play. But a stateful firewall would block this kind of return traffic.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!