That's the funny thing. Its working properly for the most part. The daemon, in.tftpd, is supposed to run because of the file, TFTP, in the xinetd directory. This file specifically tells xinetd what to run. TFTP itself generates a PID, and is listening on an address. The daemon can't communicated with whatever socket its supposed to when a network connection is requested. the other stupid thing is that I completely reloaded the operating system and the communication error still exists.