NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Change sFTP Port 22 to Stop Internet Trolls from banging on 22
sFTP Port 22 works fine, but I get Trolls from China & Turkey constantly banging on 22 trying to get in, which appear in my Router logs. How can I change the settings on the 51600 v6.4.2 to accept a...
DDNS now works for Filezilla and on my Android Phone using Solid Explorer FTPES Protocol on non standard Ports.
Want to thank you for your timely and patient guidance on this issue. Seems there are still things to learn :smileyhappy:
My Router is a NetGear_WNR3500v1. It does not have that capability...wish it did. Was hoping there was a capability in the 6.4.2 OS settings that would allow sFTP to come in on a different port. Can you advise on the FTP setup if it can accept another port?
Thanks
TomBlack wrote:
My Router is a NetGear_WNR3500v1. It does not have that capability...wish it did.
I thought most Netgear routers did give you the ability to forward port X to port Y. I think I might have a WNR3500v1 somewhere - if I have a chance I'll fire it up and take a look.
Can you advise on the FTP setup if it can accept another port?
FTPS is also secure, and you can enable FTPS in the FTP service settings. The NAS lets you select a non-standard signaling port for FTP, and you can also set a passive port range. All these need to be forwarded in the router. For example, choose 54321 for the signaling port, and 54322-54339 as the passive port range.
In the client you use the "require explicit ftp over tls" mode (at least that is what FileZilla calls it).
FTPS is/was enabled, and I had passive ports set, forwarded the middle port in range to the NAS
Entered the passive port number in Filezilla, I get this error message in Filezilla:
Connection attempt failed with "ECONNREFUSED - Connection refused by server"
If I let Filezilla use its default port which is 22, it goes right in as long as 22 is redirected to the NAS.
There needs to be a fix or a valid procedure for this to combat all the trolls out there banging on default ports. I changed my default remote access port because of this and the trolling stopped.
you are choosing ftps in filezilla?
That works for me with a non-standard control port set in the NAS and forwarded in the router (of course it is also set in filezilla).
You do need to use explicit ftps in filezilla.
The only procedure that shows a directory listing in Filezilla on the NAS is port 22. I can get a connection on a non-standard port, but not a directory listing.
NetGear should publish better procedures, and address non-standard ports because of all the Trolls out there.
It should not be this hard and much more transparent!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
