The TFTP Server in 3CDaemon offers the following features:

    RFC 1782, 1783 and 1784 are automatically implemented in the server, and require no user configuration. If the client asks for the option, and the server can provide it, it will be provided.

Here is the configuration screen, and what each value means:

tftpcfg.jpg (23895 bytes)

Create directory names in incoming file requests? If set, this will allow requests from TFTP clients which contain embedded directory names, to have those directories automatically created. For example, your Upload Directory is set as C:\TEMP\. The Client requests to send the file "/foobar/foobar.bin". The file which will be created is C:\TEMP\foobar\foobar.bin, even if c:\temp\foobar\ does not exist. It will be created.
Allow overwrite of existing files? If a client does a Write Request, and the file already exists on the server, will it be overwritten? If this option is checked, the file is allowed to be overwritten. If it is not checked, the client will get an "Access Denied" message. If the file exists, but is marked "read-only" on the server, even if this option is checked, the client will get an "Error accessing file" message, and the file will not be overwritten.
Upload/Download directory: This is the directory from which the TFTP Server will serve files. Either type in a directory name, or press the "..." button and pick a directory from the pop-up list.
Per-Packet Timeout in seconds: This will determine how long the TFTP Server will wait for an acknowledgement of a packet before it retransmits the packet. In general, the default of 5 should be sufficient. You may want to put it higher if you have slow links, or a slow TFTP Client. If the client does RFC 1784 TimeOut negotiation, the timeout proposed by the client will be accepted, and will override this value.
Maximum Retries: The number of times that an unacknowledged packet will be retransmitted before the TFTP Server considers the transfer as "failed". The default value of 10 should be sufficient for most applications.
Interframe Transmission Gap: Causes an X millisecond gap to be inserted between frames transmitted by the server. Shouldn't ever really be required; Just something I was fooling around with. Leave this set to 0 (default). Trust me....