luoj02 at tartarus.uwa.edu.au
2004-Mar-16 03:03 UTC
[syslinux] about pxe booting, no boot filename found
hello, I have a problem about pxe booting. I have two isolated machines, one(server) has got dhcp and tftp servers working correctly ( I am pretty confident with this). The other machine (client) using floopy to boot with pxe-request. The problem is, the client cannot get the bootfile("/tftpboot/pxelinux.0"), it always report no boot filename found. I also found the IP address, which server assign to client, is also refused by client, since the "discover" process keeps running. I guess it is possible because I dont have "pxe-boot server" working properly. There are many possibilities, is there anyone with similar experience or got the answer? Thanks a lot! Chris
R P Herrold
2004-Mar-16 04:02 UTC
[syslinux] Re: syslinux] about pxe booting, no boot filename found
On Tue, 16 Mar 2004 luoj02 at tartarus.uwa.edu.au wrote:> cannot get the bootfile("/tftpboot/pxelinux.0"), it always report no boot > filename found. I also found the IP address, which server assign to client, is > also refused by client, since the "discover" process keeps running.> There are many possibilities, is there anyone with similar experience or got > the answer? Thanks a lot!tcpdump will show you; high logging, as with atftp may show you; you may have a physical layer issue (slow spanning tree negotiation, or some such); http://www.owlriver.com/tips/tcpdump-tech/ http://www.owlriver.com/tips/tftp-xinetd/ address the techniques, and the second, may address your issue such taht you can see where the conversation is falling apart. -- Russ Herrold
luoj02 at tartarus.uwa.edu.au wrote:> hello, > I have a problem about pxe booting. > > I have two isolated machines, one(server) has got dhcp and tftp servers > working correctly ( I am pretty confident with this). The other machine > (client) using floopy to boot with pxe-request. The problem is, the client > cannot get the bootfile("/tftpboot/pxelinux.0"), it always report no boot > filename found. I also found the IP address, which server assign to client, is > also refused by client, since the "discover" process keeps running. > > I guess it is possible because I dont have "pxe-boot server" working properly. > > There are many possibilities, is there anyone with similar experience or got > the answer? Thanks a lot! >What does your DHCP configuration file look like? Note that if you're using the -s /tftpboot option to the tftp server, you should specify `filename "/pxelinux.0";' not `filename "/tftpboot/pxelinux.0";' -hpa