Setting up an FTP server in Windows 2000?

[AmazonRasta]

I want to set up an FTP server, but I'm not quite sure how. I'm running Windows 2000 and I have a cable modem (Rogers@Home) so I'm assuming my established connections would be half decent.

Anyways, do I need to download a seperate program or can I do it in Windows 2000. Any/all help will be appreciated. Thanks.

 

[dweezill]

don't do that with windows 2000 ftp server, you don't have a lot of flexibility, have to create acount or activate the guest account which is not very secur, use an other program like servu

 

[Techwhore]

I agree, the FTP service that comes with IIS 5 is alright, but there's better out there. Serv-U, as dweezill suggested, is a good and easy FTP service. I personally use WarFTP, it can be a little more complicated but it has great flexibility and control.

 

[syf3r]

however, serv-u will NOT allow people to connect to you via passive ftp if you are behind a firewall. behind a firewall, serv-u will only function in streams mode. you said you're on a cablemodem, so you ARE running a firewall, i hope... please say you're running a firewall... if not, use zonealarm. best personal firewall out there. stay away from blackice.

bpftpserver is the old GENE6 ftp server merged with bulletproof ftp. go here. current version is 2.15. it has a specific setup feature for a passive range of ftp ports. that way you give people your ftp address (123.45.678.90) and a port (2155) and set up your firewall to allow incoming tcp connections to port 2155. that will work for streaming mode connections.
then, in bpftp server you set up a passive range (i.e. 2155-2300). that will work for passive mode connections. if you use serv-u behind a firewall, and people try connect by passive ftp, they will be able to connect with no problem, but when they try to refresh their directory listing, it will just hang and never show anything...

so, go with bpftp server... then, download firedaemon and add your ftp server as a service under win2000 so it will be running automatically after a reboot even if you don't log in to the machine... do not download the latest beta of firedaemon. it has some kind of recursive bug in it that sometimes will try to load hundreds of copies of firedaemon. if you need an older copy of firedaemon PM me and i'll send it to you.

syf3r.

 

[syf3r]

hmm.. well, i just checked serv-u ftp's site and it seems their newest version corrects the passive ftp problem, so you may want to go with serv-u. bpftp has been great for me so far though...

-syf3r.

 

[psychobabble]

if you opt for features and options, hands down - G6FTP server is the one.
now it's merged with bulletproof-ftp.

If you aim for a high-volumn ftp site, go with IIS5 + ISA server

 

[Need4Speed]

besides, the firewall has nothing to do with Passive and Port modes...all a firewall does is block ports. It's NAT that can be difficult to work with FTP, especially if both the client and the server are doing NAT.

 

[syf3r]

passive ftp requires a range of ports in which to operate... if you connect to an ftp server under passive mode, (say, 123.45.67.890:2155) then your first connection will be to port 2155 on the server machine. as soon as you so a directory refresh, you will now be moved to port 2156. when you change directory, you will do so on port 2157. when you go back down a directory, you will use port 2158. etc etc... what passive mode does is allows you to connect through the firewall on port 2155, and then the ftp server itself handles the port switching by maintainning a control connection inbound and outbound.



<< passive port range definition for server behind router and LAN >>

taken from serverwatch.internet.com review on g6 ftpserver
http://serverwatch.internet.com/reviews/ftp-g6ftp.html



<< I do not permit passive FTP inbound through my firewall to our FTP server.
There is something about opeingin access to 64,000 ports that just does not
set well. >>

Firewalls-Digest V7 #116

the point here is that if you can enable outgoing connections on high-numbered ports you're okay, but in order to do so you're taking away some of the strength of your firewall.

these are just two notes i found (maybe not the best ones) but if you do a quick search on google for &quot;passive ftp firewall problem&quot; not in quotes you'll get tons of info on why passive mode doe snot work well behind a firewall.

-syf3r.

 

[Need4Speed]

yes, thats true, but the true problem arises when the ftp server passes the ip on to the client. if the server is behind a router doing NAT it passes along the IP of the LAN rather than the WAN. the client will then try to connect using that IP and of course since it is nonrotable, it wont be able to. the firewall has nothing to do with that...all you have to is make sure you have the ports open. but if you r running NAT and even if u have the proper ports open and forwarded, the server has to have the ability to pass on the WAN IP. G6 for instance has a setting to enter the WAN IP so PASSIVE will work properly behind a NAT.

Again, opening ports is easy from a firewall standpoint, making sure that the packets are assigned the right IP and coming and going correclty behind a NAT is an entirly different story.

In order to fully understand the way NAT affects server/client, I suggest you get familiar with the way PASV vs PORT works on FTP. If you are interested in this sort of reading you can PM me and I will be happy to help you out....