Hi all,
sory, I hope its not off topic....
I'm trying to set up my server on a non-standard port and my computer is located behind a linksy wrt-54G router.
lets assume that my non-standard port is42000. I know that I of course have to open this port and apparently the port just under this one so 41999.
In fz server, I've set up the port range from 41999 to 41999. But, when i try to connect fropm a remote machine, everything is not working as expected. Most of the time, I can't list in passive or active mode.
so, could someone guide me through a setup process which will work with a non standar port. Have I to open a wide range of ports in my router? If I can avoid this... and, how to correctl y setup the passive settings? I have a static IP.
Thanks if you can help.
Problem running ftp server on a non-standard port-
Moderator: Project members
Problem running ftp server on a non-standard port-
regards, Sof
You need a wide portrange for the passive ports. Otherwise it will not work. Ftp is doing a lot of connection attempts and it could take several minutes before the first connection times out. With too narrow portrange it's ports are soon eaten up by the back and forth going requests and answers from one client. With several clients even faster.
From the other end seen as no connect, or connect and then it times out.
Hopefully you have opened ports and forwarded them to ftp computer. Both in router and firewall. Do not use XP firewall if you want to being able to respond in passive mode. (To hard to set a decent portrange in that one.)
From the other end seen as no connect, or connect and then it times out.
Hopefully you have opened ports and forwarded them to ftp computer. Both in router and firewall. Do not use XP firewall if you want to being able to respond in passive mode. (To hard to set a decent portrange in that one.)
You need to open and forward port 42000 +passive port range.
In some routers you have to set rules to allow outgoing (20 in my case) + passive ports.
I have also a software firewall where I bind those ports to Filezilla.exe. Only application allowed with those ports are Filezilla.
When I do a security check at http://www.grc.com "shields up" I get port 21 as open and the rest are not seen. Passive ports are not seen unless used by a client. When nobody is connected only port 21 visible, with the settings in router and firewall I use.
In some routers you have to set rules to allow outgoing (20 in my case) + passive ports.
I have also a software firewall where I bind those ports to Filezilla.exe. Only application allowed with those ports are Filezilla.
When I do a security check at http://www.grc.com "shields up" I get port 21 as open and the rest are not seen. Passive ports are not seen unless used by a client. When nobody is connected only port 21 visible, with the settings in router and firewall I use.