× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Re: .net FTP client cannot connect to readyNAS FTP Server

FFH4500
Aspirant

.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.

 

Any thoughts?

 

Cheers.

Model: RN31400|ReadyNAS 300 Series 4- Bay
Message 1 of 5

Accepted Solutions
StephenB
Guru

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.

View solution in original post

Message 4 of 5

All Replies
StephenB
Guru

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?

Message 2 of 5
FFH4500
Aspirant

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.

Message 3 of 5
StephenB
Guru

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.

Message 4 of 5
FFH4500
Aspirant

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.

Message 5 of 5
Top Contributors
Discussion stats
  • 4 replies
  • 2452 views
  • 0 kudos
  • 2 in conversation
Announcements