This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
.net FTP client cannot connect to readyNAS FTP Server
Hi all,
We have some software written in .net for some equipment that uploads data to an FTP server. I can connect to the NAS with a Filezilla client however I am unable to connect with the .net client written into our software.
I would have thought if I can connect with Filezilla there would be no issues connecting with the .net client. I did not write the software so I cannot answer technical questions about it.
Re: .net FTP client cannot connect to readyNAS FTP Server
Is the filezilla server also using the same DNS/DDNS name?
Check that the passive port range for FTP is configured reasonably on the NAS (2-4 passive ports per simultaneously connected device) and that those ports are opened in the firewall. Port numbers should be between 49152 and 65535.
Masquerading might also need to be on if there is a NAT router on the path. The Filezilla client doesn't need that setting but other clients do.
Re: .net FTP client cannot connect to readyNAS FTP Server
Is the filezilla server also using the same DNS/DDNS name?
Check that the passive port range for FTP is configured reasonably on the NAS (2-4 passive ports per simultaneously connected device) and that those ports are opened in the firewall. Port numbers should be between 49152 and 65535.
Masquerading might also need to be on if there is a NAT router on the path. The Filezilla client doesn't need that setting but other clients do.
Re: .net FTP client cannot connect to readyNAS FTP Server
Well this is a little embarrassing, having a comma instead of a full stop in the IP address of your Masqueraded IP will do it everytime!! Stupid fat fingers..
Thank you StephenB, you at least pointed me in the right direction to find the I D 1 0 T error.
