easiest 3C Daemon, I use it to update my website :)

Download 3Cdaemon
http://www.firewall.cx/download-s01-ftp.php
http://sec.spruce.se/fw1/archive/

Setting up 3CDaemon to act as an FTP server

First start up the software – consider putting a shortcut to it in your startup folder so it will start each time the PC/server boots up.
You navigate through the menus using the navbar on the left, click the button that says “FTP Server” and click it (it’s a bit like an outlook menu:0)

1.      To get up and running click the “Configure FTP Server” Icon that looks like a pen knife”
2.      The “User Directory” is where all the FTP files will be stored you can change this location should you wish.
3.      The first Page “FTP Profiles” is where you set up your users. By default the only user is anonymous, if you want a secure system you may want to remove this user. (By clicking the “Delete Highlighted Profile button)
4.      To add another user, just start typing and you will be typing in the profile name box. Enter a username. In the “User Directory” section you can set up what you want the user to have rights to do, i.e. download, upload, and rename files etc. Set the rights you wish to assign to the user.
5.      You will now need to create the users password, click “Set/Change Users Password” enter then re-enter to confirm the password, then click “Cancel”
6.      You MUST now click the Save Profile button.
7.      You will get a dialog button stating the profile was saved: just click OK.

Now you can test the FTP service

1.      Open a command prompt Start >Run >type “CMD” {enter}
2.      Type “telnet <ip address of your ftp server>” {enter}

You should get a message that looks like

220 3Com 3CDaemon FTP Server Version 2.0
User (<IP Address:(none)):

3.      Enter your username
4.      Enter your password

You should get

230 User logged in

You can now use standard FTP commands


!                delete          literal         prompt          send
?                debug           ls              put             status
append           dir             mdelete         pwd             trace
ascii            disconnect      mdir            quit            type
bell             get             mget            quote           user
binary           glob            mkdir           recv            verbose
bye              hash            mls             remotehelp
cd               help            mput            rename
close            lcd             open            rmdir

5.      If you get stuck use “?{enter}” to see a list of commands
6.      You can also connect to the FTP server using software for example CuteFTP or my favourite is LeapFTP.

As for the script, there is a massive amount of questions in the MS-DOS PAQ on methods of doing this :) what exactly do you want to do?

What port does it use?

I was asking about a secure FTP server, not one that is insecure.

>>I was asking about a secure

FTP security depends on user password security, and runs over port 21

I thought it uses port 23?

What about using secure channels?

are you trying to set up SSH? (and yes Telnet does run over port 23 port 21 is the telnet control channel)

Yes SSH, I believe.

https://www.experts-exchange.com/questions/20240034/Secure-FTP-uploads.html?query=ssh&searchType=topic

As with most things, there are many ways to do this and which one works best for you depends on your circumstances.

Encrypted files:
   * Use standard FTP, but encrypt the individual files being transferred with e.g. PGP
   * Doesn't require system-admins to install special software, but does require the
      application to have PGP, or similar, capabilities. Also requires key exchanges.

FTP/TLS
  * Use FTP software that supports SSL/TLS extensions to FTP to encrypt connections
  * Requires system-admins to install special software (see
     http://www.ford-hutchinson.com/~fh-1-pfh/ftps-ext.html)
  * Requires applications to make extra calls to 'PROT' to initiate session encryption

SSH/SCP/SFTP
  * Don't use FTP but instead use SCP or SFTP, which encrypt connections
  * Requires system-admins to install special software (see www.openssh.com)
  * Requires applications to call scp (rcp-like interface) or sftp (ftp-like interface)
     instead of FTP

IPsec
  * Use IPsec to encrypt all network connectivity between systems
  * Then doesn't matter what the applications do underneeth
  * Requires system-admins to setup IPsec connectivity
  * Not supported on all OS's

Well its just a quick upload to a remote ftp server daily.  I am not sure what FTP server they use...  What is best for that?

FTP by its very nature is insecure

the protocol sends authentication in plain text, anyone running a packet sniffer can see your password.

You might want to think about  using a VPN?

If you're that concerned about sending unencrypted over a trusted, private WAN link, then you should be concerned about having those files unencrypted and sitting on your file server, or indeed your workstation itself !
My advice - encrypt, and then send (using FTP).  At least then only authorised recipients (with your key) will be able to decrypt.
Even something like WinZip pasword protection would suffice - just give the password to the end user over the phone in order to decrypt ?  This would certainly serve casual means, but it's not an industrial strength strong crypto solution.

Also see...

https://www.experts-exchange.com/questions/20994102/FTP-site.html#11269377