Passive probs w/IIS 6, FTP server & Linksys Router

Oh man, where do I begin? OK—I am an internet dilettante, so maybe you folks can help me out! I need to configure my system so that people can access my FTP site from within a web browser, which I haven’t been able to achieve. I am running Windows 2003 Server off of an old PIII 800 MHz machine, behind a Linksys BEFW11S4 wireless router. I have another PC on the router as well for surfing the net. So, I have set up the router for port forwarding of 20 and 21, as well as enabling ports 5100-5700 for passive connections , and have as well configured 2003 server with an FTP site through the IIS Manager. I have even done a registry edit from Microsoft to free up ports 5100—5700…here is the official link. http://support.microsoft.com/defaul...kb;EN-US;196271 .In addition, I have enabled UPnP forwarding on the router and enabled HTTP and FTP settings to go to my server’s local IP. I have a dynamic IP from Time Warner cable, and I have a program from no-ip.com to update my DNS info—both for my website which I host as well(which works fine) as for the ftp site.. OK…I can access the FTP site through an FTP client like cute ftp, but only using a PORT setting—I can upload and download no problem. Passive connections seem to get kicked off. People have been ULing and DLing successfully so far in PORT mode only. When I try to log in to the FTP through any web browser, a username/password box pops up, I enter the U/P that I set up(with permissions) and I get a message “426 Connection closed; transfer aborted”. When I look at IIS current sessions, it shows I am logged in for a couple of seconds before I’m kicked out. Is there a problem in getting web-based ftp connections due to a passive issue? Maybe one of you folks can straighten this mess out before I lose my hair! I am getting to hate Linksys and Win2K3 Server!

THANKS IN ADVANCE!

Bump!

You can't just 'open up' ports whatever you said they were...
The client makes the connection, not the server, in passive mode. You will have to forward all those ports to your ftp server.

That would explain what you've experienced... Client initiates connection to server, logs in. Server hands out random port number. Client tries to connect to specified port, but the router doesn't know where to send the connection. Server times out, logs out user...

I did forward all ports 5100-5700 in the router. Is that what you mean?

Sounds like English to me...
What I said is what I meant. Yes, you will have to forward those ports. I also said forward to your ftp server, not 'in the router', whatever that means. Did it work or not, by the way?

As a noob Im not really sure how to do that.

Can you explain the details?

Thanks

Well, I'm not sure it can be done on all routers. Every router is different, I can't really just give you directions. Mine has a virtualserver option, but that will only allow one port to be forwarded at a time. For hundreds of ports, that doesn't sound like the best idea....

You might try a DMZ (demilitarized zone), your router should have support for it somewhere. Set your server's ip to be the demilitarized zone. That should work.

Other than that, check out something like a virtualserver option in your router's config, and see if you forward multiple ports at a time with one entry.
Good luck, hope you find something to get it working...

I have ports 5100-5700 forwarded on my router, as well as ports 20, 21 and 80.