Hello

 - test with "tcpdump" or like, if the Indy does send the bootp requests and if 
they are answered
 - use "setenv DEBUG 1" to get more information from the indy
 - as you don't use any bootp-ip (like in 
bootp()192.169.1.1:/tftproot/tftpboot.img), make sure you get the correct IP,
   your bootp server listens to it, or try it with correct ip
 - Don't let the tftpboot server use high ports (>2^15-1, AFAIK), as those 
might cause problems

Hope, this might show you where to look for errors.

CU,
        Achim

Reply via email to