WarFTP Daemon for Windows

User Reviews

• Highly functional and it's free but not for beginners

  MikeBuddDecember 12, 2012

  Pros

  - user, group and folder management facilities - multiple virtual servers - stable (so far) - upload and download management - graphing of server load, and continually updated stats - a real server! - highly configurable, from technical parameters to user parameters and server messages (which themselves can be tailored per server, user or group) - automatically sets itself up (some server software doesn't !) Particularly suitable if you want to run your own public file sharing service.

  Cons

  Capabilities: - no total per server bandwidth restriction (per user restrictions are supported) - large ftp download services may hit concurrent user limits Usability: - suitable for intermediate and advanced users no beginners.

  Summary

  Intermediate users should note the following to save time: - in the WAR world most things are users (for user read agent) so even a virtual server is seen as a user of the software. This means most tailoring takes place via the user database. Most of what doesn't is in the advanced server properties (which apply to all virtual servers) - permissions are a strict inheritance hierarchy, some cannot be changed lower down the tree, you must change them at a higher level. This includes folder access restrictions. - the sysadmin user has limited FTP privs by default for security reasons. Best to set up an FTP user for yourself. - the server autodetects the computer's primary connection on start up. This can lead to problems if you are using an encrypted internet connection service, or both wired and wireless connections. So disconnect before starting the server. (there is doubtless a way to turn this off) - one of the problems this causes can be that the server interface refuses to connect to the server. To get round this, you can type in the correct values (normally port=0, IP=localhost when you log-on via the GUI) - I have found you need to test your server from a remote site, or by using a proxy. Trying to test by acting as a remote user from your own IP can cause difficulties, possibly due to security restrictions, though this is probably tailorable if you know how - the server is not in multi-threaded mode by default, this is set in advanced properties - configuration for use behind a nat router is by editing a nat.config.sample file in the program directory, not by editing the system or other server's admin config tab. (In interpreting this remember such servers are users). Indeed you need to be careful in editing the domain setting this tab as it is difficult to return to default (blank) settings. - this software was originally coded for XP, so it may be worth running in XP compatibility mode, though i have noticed no difference - Jgaa's restrictions on government IPs need to be removed by disabling inheritance from a higher level, or setting use this level only, on the IP restriction's the virtual server's user database record<br /><br /><span class='notifyMsg'> Updated </span>on Dec 12, 2012<p/>Oh should have said all the above should be qualified by 'as far as I know' . I have only been using this software for a short while. Also: 1) If using the nat.config file, you need to rename the nat.config.sample file to nat.config, and comment out any unnecessary lines before starting the server 2) IF you need to cnage the log-on settings for the server GUI interface t log on, then you need to save these to default.wdm to resolve the problem long term 3) The server declares to the client that it does not support non-ascii characters. I'm not sure what that means - possibly in commands for security reasons? But I don't think there are any non-ascii FTP commands. So far it does not appear to affect what you can use it for, but it might affect use in non-latin languages maybe.<br /><br /><span class='notifyMsg'> Updated </span>on Dec 12, 2012<p/>Oh should have said all the above should be qualified by 'as far as I know' . I have only been using this software for a short while. Also: 1) If using the nat.config file, you need to rename the nat.config.sample file to nat.config, and comment out any unnecessary lines before starting the server 2) IF you need to chage the log-on settings for the server GUI interface t log on, then you need to save these to default.wdm to resolve the problem long term 3) The server declares to the client that it does not support non-ascii characters. I'm not sure what that means - possibly in commands for security reasons? But I don't think there are any non-ascii FTP commands? So far it does not appear to affect what you can use it for, but it might affect use in non-latin languages maybe.

  ---