Russell McMahon wrote:

> Have just ventured into the new (for me) world of running a website 
> from own LAN.
> Trial page here (*very* slow uplink )(just a randomish collection of 
> pictures at present).
>
>        www.russell.servepics.com
>
> Server is the free and marvellous Apache 2 running on Windows XP home.
>
> Requirement:
>
> 1.    I'm looking for recommendations for an FTP server to allow both 
> upload and download of web content, also running on Windows. Ideally 
> it would be the same price as Apache (ie free) but for-money products 
> OK if there's an excellent reason to use them. Ideally would run on 
> all flavours of Windows. Would consider using Linux in due course (of 
> course) but at present Windows is what's available and easy for me. 
> Aims are: works, easy to install and run, no surprises.
>
> I could Google on this (and have) BUT "the eyes and brain of the 
> PICList" are liable to be able to identify a far better solution that 
> I am liable to by myself. [eg Googling: "ftp server" freeware gives 
> 8000 hits including eg 
> http://www.gold-software.com/ThePersonalFTPServer-review8282.htm].
>
> 2.    Also possibly a POP3 email server, although that, as far as I 
> understand it, may need special external support and can not be a 
> totally free solution.
>
> Getting Apache running was surprisingly painless (only a little blood 
> and sweat and no tears)(fighting the router/firewall was the greatest 
> hurdle).  If adding FTP access (and possibly email) is as easy I can 
> see the possibly of writing it up as an integrated procedure for others.
>
>
>
>        Russell McMahon
>
Hmmmm Linux is my friend.... but still.

Regardless of your intended OS, you will find that FTP is very "blood 
sweat and teard" when behind a firewall. The FTP protocol requires 2 
socket connections between client and host. The problems is that the 
"old" way of doing things was to have a "control" connection FROM client 
TO server, and then a data connection FROM server TO client. This 
presents a great deal of frustration if the Client is "Natted" behind a 
firewall (the firewall will block the incomming data connection (well, 
most do). The "new way" is to use "passive FTP", where the client makes 
the data connection from the Client to the Server. The problem here is 
that the Server's firewall will block the new data connection.

You need to have a fancier-than-most firewall on your server side to 
manage FTP.

Do some research.

Rolf
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist