I´m about to set up a ftp-server for the first time, behind a firewall/router.
I appreciate your help and advice in this matter. I´ve DL both Bulletproff and Serv-U but what is to prefer, maybe something else?
My ISP handle me a dynamic ip so I have signed up with dns2go.com.

TIA
IB



Last edited by IB at Jul 17 2002, 12:02 PM

I prefer Serv-u - I find it's easier to make changes and add things as you need them. You can also have multiple domains depending on the individul axx you want to give.

with bullet proof you need to make a text file for any virtual drives and such, you also can't have multiple domains. as with Serv-U you do it all right in the prog.

thanks Leech,
I´ve heard that there is a problem with Serv-U and dynamic IP´s, running Serv-U in PASV-mode, You had to run it in PORT-mode to get it up and running....can anyone confirm this...? :(

Cheers
IB

I have used GuildFTPd for some time, now I have started to experiment with Blackmoon. Guild is nice, easy to setup and free. Blackmoon seems at first sight to be nice, easy to setup and can be downloaded as a 30-day-trial.
Btw, this question is an oldie, asked several times at different boards and always with different answers. Bulletproof and Serve-U seeems to be the most popular ones. I have never tried Serve-U really, Bulletproof (G6) has screwed things up for me. RaidenFTPd was wonderful, but a pain to setup.
Get inspiration at h**p://serverwatch.internet.com/ftpservers.html

May I also dare to recommend Jessica's thread I'm Thinkin' Bout Startin an FTP at http://www.betaone.net/forums/index.php?ac...528033c2fbeb60b which might be to some use... ^_^

thanks .unicorn....I´m working on it and I´ve read your 3 "steps" and also that thread started by Jessica.
I can login from my local LAN to Serv-U(v 4.0.0.4) and everything seems nice, I can upload and download...but the problem is when I try to access from the outside?!
I have a Netgear RT314 router/firewall, so the problem is, I guess, to config - forward the ports to my servbox. And the reference manual for this router could be better:( but sooner or later I will find the solution.

Cheers
IB
:D :D :D

I have a router and dynamic ISP. I generally use Serve-U 4. For awhile I was using dns2go so that I didn't have to see what my ip is (so I let the other party know) The main thing is forwarding the ports. If you use port 21 it should be just a simple click in a box on your router setup screen. If you want to use a different port then you need to open up a series of others so there will be enough sockets open. Dns2go is free, btw and it works well. Essentially it translates your dns2go address to whatever ip you've got showing from your isp.


Btw, I've also experienced the problem of not being able to understand how to set up the router. Particularly difficult for me was an SMC that I got rid of in favor of a BEFW11S4 v.2 Linksys. (4 ports/wireless). Linksys published a much better manual with this model and made some great enhancements to the setup menu.



Last edited by rikytik at Jul 19 2002, 09:07 AM

Yep, ServU rulez :)

I used ServU for a while now and there are only two bad things I can say about it. First thing is that it seems to handle reverse lookups incorrect (that is, when restricting access on hostname instead of IP address it fails to lookup the IP address of the given hostname) witch makes restricting access a bit more difficult. Nobody seems to have the answer to this.

The other thing is a rumour that I couldn't confirm myself. The rumour says that ServU isn't handling bandwitdh good, and wastes bandwidth compared to other FTP server programs. I've compared ServU myself (to Bullet and MSFTP) with one large files and with many small files and in all case the I didn't detect any difference (except for MSFTP).

Cheers!

@IB:
One little thing - the first time I tried to setup one of those small nice boxes I couldn't make it work. Then I :wacko: found out that you had to reboot (a matter of 2 seconds) the box for some changes to have effect. Now I guess you allready found this out, just a thought here.

thanks for your support...but for the moment I got stuck.
I can connect from my local LAN and transfer files...but when my friends try to connect from the outside they CAN connect and LOGIN...BUT when the command "list" is given...there is a timeout...they never see the directories in the "ftp-root-directory".
I have read, somewhere, that the solution is to setup the local LAN with static IP instead of DHCP-mode... and I have done this too...but without sucess.....

This is my config:
OS: Win.Net 3621 standard server
Router: Netgear 314 (firmware 3,25)
Dynamic IP(from my ISP-provider): Yes
FTP-server: Serv-U ver 4.0.0.4

What am I doing wrong? I must have missed something...maybe in the setup....

I appreciate your support :P

TIA
IB
:) :) :)

Hey IB, If they can connect from the outside they obviously get some contact with your server. So, wait a moment before you reconfig your LAN.

If I get everything right this far you have configured your router to forward all queries from the outside to your server, or rather all queries at port xxxx to your server. Then the client and your server shake hand, get pretty well along - as far as they use port xxxx (the so called control connection). Then when it comes to file listing the data transfer channel is used instead: port yyyy. Most ppl are using some sort of firewall today and those won't accept unexpected traffic. Thus they have to use PASV mode (where the client tells the server to go for port yyyy and send data there). This in turn forces you to config the server to allow PASV mode and maybe also allow a port range. Check this, give it a port range not less than say 1000-5000 or something. Then check that your router allows theese ports, or config it consider your server as a demilitarized zone (DMZ-mode). Ask your friends to connect again and tell them to make sure they config their clients to use PASV mode and then maybe also tick any choice available for "Site uses NAT/IP Masq/Non-routable IP" (or something alike it).

Then please get back here and tell us about it.