Configuring a FTP Server
Posted: 2004-06-08 by Achilles |
Testing
Now that a basic user is set up and the FTP server is running, it is time to test that everything works. Open up another command prompt window through Start->Run->command. Type in "ftp" (sans quotes). The prompt should change to ftp>. At this point type in "open localhost". If the server is running there should be a server message that is relayed back along with a prompt for a user name. Enter the username and password when prompted (remembering that they are case sensitive). If there is no prompt, the server is not running and it should be restarted by finding the FileZilla Program Files group and clicking on the Start FileZilla Server icon. If the username password is rejected, double check both the username, password and caps lock. Additional information can be found on the FileZilla Server Interface Window
The next step is to make sure that the contents of the directory can be accessed. This can be acheived by typing "ls" which lists the files in the current directory. If the contents look right then it is alright. Next step will be to actually get a file using the command "get
Advanced Features
Limiting the Number of Users
By default, FileZilla is set up to allow unlimited users. This might not be something that is desirable. There are also options to allow for timeout settings. This is important with a limited number of uesrs - if a connected user is not actively doing something it might be a good idea to have a short time out / transfer value to clear space for others.
Rate throttling is another great feature. Say you just discover a long lost Uncle Bob and he wants to catch up with the last 10 years of pictures. Well you can throttle Uncle Bob and his huge downloads by limiting the rate he can download pictures at so that dear Aunt Rita can get pictures from last week's birthday at a decent speed.
There you have it. Setting up a FTP server is quick and easy especially with a great program like FileZilla. FTP makes distributing many files or large files much more practical than HTTP and is ideal especially for something like distributing digital photos.
Questions, comments, concerns? Bring em up in the forum
Conclusions

