PDA

View Full Version : ioFTPD vs. RaidenFTPD


ioUSER
05-18-2006, 07:17 PM
Hi...

i use on one machine ioFTPD 5.8.5r if i wanna upload there its really really slow.. then its getting slower to about 0,1 kb/s.

if i use on the same machine same link RaidenFTP (same settings) i get normal speed... what could i have done wrong?

thanks for help ioUSER

olivilo
05-20-2006, 12:18 AM
I currently use both also.
No problem over here.
U have firewalls properly set up?
Both Regged?

ioUSER
05-20-2006, 10:06 AM
hi yes both regged and confed well... on another link its working just nice...

Zer0Racer
05-20-2006, 11:10 AM
Probably problem with settings in router and/or firewall. You should forward not only the port you connect to (ie. 9999) but also that port -1 (ie. 9998) for active transfers and also the dataports you've set up in ioFTPD.ini (default 1024-2048). Though I would recommend setting portnumbers above 5000. You should also make sure you've got enough dataports for the numbers of users that are logged in at one time. A rule of thumb is to let each user have between 10-100 ports available. So 10 simultaneous users would make at least 100 ports open or 1000 ports to make sure ioFTPD won't run out of ports ie. transfer of many small files that occupie one port each (and it takes N seconds before windows can close the port(s) and make it available for transfer again).

If your router does not support port forwarding it uses port triggering that is not as reliable. It can close a number of ports if the triggering ports haven't been used in some time, ie. during transfer of big files on not so fast network etc.

If your firewall does not allow ioFTPD to use ports like 9998,9999 + the dataports you might run into trouble. Make sure the ports you use are allowed and/or that windows firewall is disabled if you use a third-party firewall like kerio or norton or whatever.

If you are behind router/NAT don't forget to setup ioFTPD.ini properly ie.
Host = <external ip.. routers ip.. NOT internal ip>
Bind = <your local ip.. internal ip ie. 192.168.0.2>

Hope it helps

ioUSER
05-21-2006, 01:03 PM
thanks zer0racer i will try it and post status here :)

ioUSER
06-01-2006, 12:17 PM
hmmm it seems the isp is the problem... on any other isp then this one it works just fine... i'll do a little more testing...