trying to get pxe boot working, but fail when setting up tftp server
i am attempting to setup a boot server as per Alien's wiki but fail to set up the tftp server.
my /tftpboot folder contains:
TFTP E32 open timeout error.
In a bold move , I tried to run the tftp outside of inetd. so I commented the line, restarted inetd, verified udp port 69 wasn't used and started the tftp server as:
still the same error!
Finally, I did something more, i killed this tftp server, I renamed the /tftpboot folder and added a new empty /tftpboot folder in its place.Then i restarted the standalone server and I'd still get the E32 error!!!! how is this possible from an empty folder??
Thank you for your help!
do you have a line in your hosts.allow for in.tftpd?
Be sure your /etc/dhcpd.conf is set up correctly, that error is a PXE (client) error, not a TFTP server error.
Are the DHCP and TFTP on the same machine?
Other possibilities - are you sure the client is getting its DHCP data from the right machine?
Can you connect via tftp from another machine:
If so it would mean that the PXE boot machine is simply not finding the TFTP machine.
It's not getting an answer from the tftp server, so either like you say, it's not looking in the right place, or it's got its fingers in its ears :)
Test tftp locally and remotely from command line. Does it work?
Hello everyone thank you for the responses.
tftp works, I can log in from another slackware in the same intranet, and get a file (like pxelinux.0 or f2.txt) from command line tftp client.
the dhcp should also be correctly setup:
DHCP and boot server are on the same slackware64 machine, and there is no other dhcp server on my intranet.
OldHolborn, I don't have such a line in hosts.allow, but I don't have it in hosts.deny either, so I don't think I need to place it in hosts.allow. Or am I wrong?
What do you make of all this info, docs ?:)
is that a typo or deliberate?
Your DHCP is listening on one class C, the tftp server you are directing it to is on another
that's why I shouldn't be trying things on linux past midnight...
ok i'll go hide in a hobbit house and never come out again :)
I changed the value of next server - its a class C home network..
i'll verify this tonight, but i'll pretty confident that this was the problem.
|All times are GMT -5. The time now is 03:35 AM.|