Page 1 of 1

Problem with tftp-server

Posted: 2007/09/07 16:32:04
by Metsger
I have problem with working tftp-server on two serveres with centos-5. All servers with centos-4 are working fine in this situation.
Is tftp-server from centos-5 broken?
The PXE CLIENT when booting cannot access files in the "pxelinux.cfg" dir. I setted full premissions on tftpboot for root:root.
Example of Message log:
dhcpd: DHCPREQUEST for 172.16.0.253 (172.16.0.254) from 00:01:6c:ca:24:7b via eth1
dhcpd: DHCPACK on 172.16.0.253 to 00:01:6c:ca:24:7b via eth1
xinetd[3173]: START: tftp pid=3238 from=172.16.0.253
in.tftpd[3239]: RRQ from 172.16.0.253 filename pxelinux.0
in.tftpd[3239]: tftp: client does not accept options
in.tftpd[3240]: RRQ from 172.16.0.253 filename pxelinux.0

*** AND STOPS here **

Same problem is not only for me:
http://lists.slug.org.au/archives/slug/2007/05/msg00221.html

Problem with tftp-server

Posted: 2007/09/12 21:44:43
by woof
If you have a system on the subnet you can run tftp on, try this experiment (using the CentOS server's IP address, of course):
[code]$ tftp 172.16.0.2
tftp> trace
Packet tracing on.
tftp> get pxelinux.cfg/default
sent RRQ <file=pxelinux.cfg/default, mode=netascii>
received DATA <block=1, 226 bytes>
tftp> quit
[/code]

If you're having trouble getting the file, you'll see information why. Post that here. Example (asking for a file that's not there):

[code]$ tftp 172.16.0.2
tftp> trace
Packet tracing on.
tftp> get pxelinux.cfg/nosuchfile
sent RRQ <file=pxelinux.cfg/nosuchfile mode=netascii>
received ERROR <code=1, msg=File not found>
Error code 1: File not found
tftp> quit
[/code]

Regards,
Steve

Re: Problem with tftp-server

Posted: 2007/09/14 12:12:25
by Metsger
Problem already solved.
In centos 5 I need optinon next-server for dhcp.

Re: Problem with tftp-server

Posted: 2016/06/15 10:18:31
by patrick_brosnan
I know this reply comes a long time after the event, but just in case any of you people are still tuned into the site I wanted to say thank you for making this post as it benefited myself and a colleague who had been scratching his head over a PXE problem for a couple of weeks. The suggestion of using the tftp session allowed to realise that the name path was wrong in his configuration file.
:D