Active mode issues are generally the fault of the client (not server side).
Active mode behind a firewall/shared connection is generally difficult to
do, because listening ports need to be dynamically opened (port is
determined by the ftp client during directory listings or transfers).
Many routers provide an ALG on port 21 to listen on FTP commands to sniff
out the port that needs to be open for active mode to work. However, that
only works on port 21 in most causes.... so it doesn't work on non-standard
ftp ports.
Your best bet is to setup your FTP server for passive mode FTP (you'll need
to forward an additional range of ports to the computer running the FTP
server, specify within IIS to use those forwarded ports, and tell IIS to use
your WAN ip as the passive mode ip).
--
Jason Tsang - Microsoft MVP
Find out about the MS MVP Program -
http://mvp.support.microsoft.com/default.aspx
"pttk" <(E-Mail Removed)> wrote in message
news:27cd301c46443$3c06c6c0$(E-Mail Removed)...
> Hi,
>
> I have two out FTP service, one in 21 port and work ok,
> another in port 2121 (in another server), WS_FTP send "500
> invalid PORT comand". Both service in W2YK machine's and
> in IIS service.
>
> In my MN-700 I "open" only port 2121 to my PC
>
> Any idea?
>
> PTTK
>
>