This rings a bell to me.
I don't know if it still is true but "a while ago" tftpd was binding to
the networkcard it found first.
Try to run it on a machine that only has one networkcard and see if it
works better.
If you look at older postings you will probably find the exact problem.
Howerver what you describe might be another problem, but I spent a log
of time trying to get an old mac to boot via tftp and never succeded
until I accidently hooked the client up on the other networkcard....
Jonathan Eifrig wrote:
Rogier Krieger wrote:
On 1/24/07, Jonathan Eifrig <[EMAIL PROTECTED]> wrote:
tftpd[xxxx]: oack: Permission denied
That may have something to do with *file* permissions. Quoting tftpd(8):
"The use of tftp(1) does not require an account or password on the
remote
system. Due to the lack of authentication information, tftpd will allow
only publicly readable files to be accessed."
Are the files you're trying to serve world-readable?
Yes. :-)
As I said, the problem is client-specific: a tftp client running on
the same machine as the server can retrieve files with no problem.
Clients on remote machines timeout.
It's as if the tftpd process is not allowed to use eth0 or some such.
