Sami FTP Server

Table of Contents

I. License
II. Installing
III. Using Sami FTP Server
1. Starting up
2. The information screen
3. Statistics
4. Users
5. Settings
6. The log viewer
IV. Troubleshooting
1. "Error: Cannot initialise server socket"



I. License

Sami FTP Server is shareware, and is distributed without guarantees. The creator of the software can not be held responsible for possible damage caused by installing or using this software. None of the contents included may be modified.

You are allowed to use Sami FTP Server for 30 days for free; after that, you are required to purchase and register it.



II. Installing

Simply run the installer program, select the desired destination directory, and start Sami FTP Server. A window will pop up to greet you the first time you run the program, and you will also be directed to the Settings window after that.



III. Using Sami FTP Server


1. Starting up

After installing Sami FTP Server and starting the program, a window with a greeting text will open. You will also be directed to the Settings window; this can later be reached by right-clicking on the icon in the system tray, next to the clock.


2. The information screen

The first thing you will see when opening the Settings window is the information screen.

Here you can inspect the currently logged in clients or check the bandwidth usage or the uptime. You may also want to click the green play button in order to start the server. If the stop button is later pressed, no clients will be able to connect to the server.

Note: the currently logged in clients will not be removed when stopping the server.


3. Statistics

Selecting the statistics tab takes you to a brief summary of statistics for the server.

You can select what time span you wish to view statistics for, and then inspect the amount of transmitted data as well as what individual files were sent or received.


4. Users

In order to give people access to your files, you must add user accounts. Simply go to the users tab, add a user, enter a password to use, and then add directories to give access to.

If you wish, you can give write access or permission to create or delete directories in certain directories as well. All kinds of directories can be added - everything from normal directories to network shared ones, or complete drives.

You can also specify the number of connections each user account can make simultaneously, as well as the bandwidth the user is allowed to use.


5. Settings

The settings screen lets you manipulate the server and access settings.

The standard port number for an ftp server is 21, but you can change it to anything you wish here. Be sure to stop and restart the server for that change to take effect. The maximum bandwith allowed for the server can also be specified, as well as the maximum number of users that can be connected.

The greeting and bye messages are short messages you wish to present to users when they connect or disconnect from your ftp server. If you wish to disable logging or change the log file, you can also do that.

Ban settings shows the list of IPs you do not wish to have access to your server. If an IP number is present in this list, all connections attempted from it is automatically closed immediately. If you want to, you can enable automatic banning if people attempt to log in a number of times in a time span.


6. The log viewer

The log viewer shows you the activity during the current uptime of the server.

User requests are shown as blue, successful replies are green, and replies which shows a negative result are red. You can clear the log window, or save it as a text file by pressing the appropriate buttons. If you wish to view the whole log since the installation of the server, press Open server log....

Note: if you press Ctrl+C while you have selected a line in the log window, you will copy the contents. This can be practical if you wish to get the IP of a specific request.



V. Troubleshooting


1. "Error: Cannot initialise server socket"

This means that the port specified for use with the server is busy. Most probably another server application is using that port already. Either change the port number in the settings, or shut down the offending program and try again.