Most of the above mentioned TFTP server packages also install TFTP clients. So you need to have some documentation about the device to know how it configures itself.
Another possibility is that the device configures an ad-hoc IP network. If the device configures itself using DHCP from a server on your network then you can look at the DHCP service log files to see what its IP address is. You might also need the port number on which the devices TFPT server is listening if it is not the TFTP well-known (standard) port, port 69. The file name that the device is expecting to receive.If the device that you are attaching to the network is itself a TFTP server and you need to upload a file to that server using a TFTP client, then you need to find out
This isn't a 'native' server in the sense of being in the Windows distribution, but it is a commonly used TFTP server. If you are using MS Windows, try TFTPD32. If you are using CentOS, RHEL or Fedora try this blog post. If you are using Debian, try this Nixcraft article. If you are using Ubuntu, try this article by David Sudjiman. It is probably best to use the TFTP server (or 'service' in MS parlance) that is 'native' to the operating system distribution on which you wish to run the TFTP server.
