FlashFXP Forums - View Single Post

ratbot · 10-15-2003, 07:27 AM

forwarding is not the problem. When a client connects it should get the public ip when pasv is transmitted, otherwise it will try connecting on the 192.168.1.2 address. That is why it is important for the ftp pretetend it on the external ip. When the client issues the pasv command it trys to connect on fookeme.dhs.org port 10000-11000 in my case which the router then forwards to 192.168.1.2 and the server is ready and waiting. I know serv-u does this without a problem. However i do not wanna use that software seeing the ioftpd is superior in many ways.

10-15-2003, 07:27 AM
ratbot Junior Member Join Date: Oct 2003 Posts: 8	hrmm forwarding is not the problem. When a client connects it should get the public ip when pasv is transmitted, otherwise it will try connecting on the 192.168.1.2 address. That is why it is important for the ftp pretetend it on the external ip. When the client issues the pasv command it trys to connect on fookeme.dhs.org port 10000-11000 in my case which the router then forwards to 192.168.1.2 and the server is ready and waiting. I know serv-u does this without a problem. However i do not wanna use that software seeing the ioftpd is superior in many ways.