This project has moved. For the latest updates, please go here.


Apr 6, 2010 at 9:00 PM

Any comments? Leave them here!


Jun 3, 2010 at 6:57 PM
Edited Jun 3, 2010 at 7:03 PM

I have a problem with TFTP Server. After the server starting, why can't I  log in to the server? And is there any account management function?

Jun 3, 2010 at 7:10 PM

Hi, TFTP is a very simple protocol, not to be mistaken with FTP. It does not have any security and authentication provisions at all. If you're looking for a free FTP server I recommend filezilla ( see )



Jun 3, 2010 at 7:19 PM

Hi, OK. I see. Thank you for your suggestion. But actually I need a C# version of FTP Server implement. I think maybe I can extend your TFTP Server with authentication?

Jun 3, 2010 at 7:32 PM

Hmm I was going to reply that there are lots of FTP servers on codeplex, but now I see that they are all FTP clients. Modifying my server would not make it an FTP server, they are really totally different protocols (TFTP is UDP based and connectionless, FTP is TCP based).



Jun 3, 2010 at 7:44 PM

Yes, that is true about the ftp clients on codeplex. And actually I don't need to implement it in a proper sense of the FTP protocol. I just need to implement a server and client just like the ftp. Even just the client and server can transfer the files with authentication will be ok. But now I am not clearly about the TFTP protocol. Do you have any suggestion about the TFTP client implement or some existing examples (with C#)?

Jun 3, 2010 at 8:00 PM

I found a client here but make sure you read the comments.. they fix a few bugs in the original source.


Jun 3, 2010 at 8:17 PM

WOW, thank you. That is really what I need I think. Thank you again :)

Feb 27, 2012 at 3:59 PM
Edited Feb 27, 2012 at 6:30 PM

I would like to use it as a component in my own service, which is limited to .NET 2.0. Could you give me some hints or a sample, how to use the Library as a component?

 UPDATE: OK, It seem that I did it, it works in 2.0, thanks a lot.

Thank you!

About TFTP Clients: is OK for a client. But gave me really a hard time, when I implemented it in my project as a server. On some computers worked OK, on some nothing, on some  no ACK packet returned from clients. It took me more than one day before I discovered, that it is a flaw in the TFTP protocol design.
Source: It is just simpler to implement a TFTP server where all data transports run over unique ports, because the demultiplexing of the network packets then happens in the operating system. When the TFTP server returns all replies over the well-known port 69, it must demultiplex incoming packets itself, using the source IP and port addresses|

It is so great that you have implemented the SinglePort option, which enables the use of TFTP in routed netwok environment!


Feb 27, 2012 at 9:28 PM

Hi, I'm glad you found it useful. The TFTP protocol limitations can be tricky sometimes but you have to remember that it was designed back in the internet stone age, before firewalls and personal routers :)