- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: .net FTP client cannot connect to readyNAS FTP Server
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Any thoughts?
Cheers.
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: .net FTP client cannot connect to readyNAS FTP Server
You might want to deploy a filezilla server for testing and see if the .net client can connect to that.
Is the device running the .net software on the same network, or is it remote?
Does the .net software have any FTP settings that can be configured?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: .net FTP client cannot connect to readyNAS FTP Server
I have, they all connect to the Filezilla server no problem at all.
The devices are all remote.
There is limited config available. Username, Password and path.
Cheers.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Cheers.