TFTP Boot File Not Found

  • Be gentle - I’m not a super-techy person…

    • FOG Version: 1.4.0
    • OS: Ubuntu 16.04 as a VM on a Windows 2012r2 Server

    2012r2 server functions as DC, AD DS, DNS, DHCP

    • Service Version: 0.11.12 (Smart Installer)
    • OS: Windows 7

    IP Addresses
    Win2012r2 Server

    Activated Hyper V on windows 2012R2 Server. Installed Ubuntu 16.04 LTS, Installed Fog 1.4.0 and can successfully see from any PC in the subnet

    Ensured Win2012R2 DHCP server included options 66 ( & 67 ( undionly.kpxe)

    Installed Fog Client from server download and have added Host to FOG.

    At bootup, Host shows:

    Client IP: Mask: DHCP IP:
    Gateway IP:
    PXE-T01: File not found
    PXE-e3b: TFTP Error - File not found
    PXE-M8F: Exiting PXE ROM

    I’m looking for ideas for next steps to get this up and running for imaging!

    For instance - How do I ensure TFTP is running on FOG? And if not, how to activate it? (The blank of ‘TFTP’ above would indicate to me that it either can’t find the service or cant get to

    Your help is much appreciated! But please be detailed in your reply - I can follow directions, but am not a techspert. Thank you in advance!

  • Moderator

    @BiologyBen It sounds like pxe booting was only the beginning of your challenge. Good luck!!

    If you find new difficulties, please post to new thread and we will help you get started again.

  • @Sebastian-Roth @george1421

    Thank you both for all your help! We’ve got 40+ PC’s to image and keep operational for about 1,200 youth at our org and this will make that much, much easier going forward!

  • Senior Developer

    @BiologyBen Don’t worry. We all make mistakes and this forum is just the right place to have some extra pairs of eyes to look at things and find what’s up. 🙂

  • @Sebastian-Roth

    Absolutely correct - There was a space on my DHCP option 67. The system boots into the fog menu perfectly with it removed.

    And here I started to think that maybe it wasn’t a stupid mistake on my part! 😛

  • Moderator

    @Sebastian-Roth You are 100% correct there. I didn’t spot it until your post. I was focusing on the text not noting the extra space in wireshark when it was listing the values. Looking in the hex editor, sure enough there is hex 0x20 there (space character).

    As I was telling Ben the pcap looked perfect (minus the extra space). I have seen this condition before so I’ll need to remember this one for next time. Great find!!

  • Senior Developer

    @BiologyBen I can’t believe that it took me almost 20 minutes to spot the problem in the PCAP file. I was almost gonna ask you to capture another one where we see the TFTP reply as well. But I am pretty sure we don’t need that.

    Take a very close look at packet number 10 and 11 in your PCAP file. There is a space (hex 20) in front of the filename. Looking at your initial post I see that space now as well! Maybe copy&paste?? How funny is that!

  • For posterity sake:

    In chat, after confirming the machine MAC address, george1421 said, ‘In the pcap file, I see it requesting the file size for undionly.kpxe then asking for the first block, but it never asks for the next block since the block sizes are 1456 but the total file is 95348.’

    This is an old Dell Optiplex 580 and had bios A05 so I upgraded to A08. Unfortunately, no change yet.

  • @Sebastian-Roth

    I see the following:

    admin@fog-Virtual-Machine:~$ ls -al /tftpboot
    total 7208
    drwxr-xr-x  6 fog  root   4096 May 30 19:51 .
    drwxr-xr-x 27 root root   4096 May 30 19:50 ..
    drwxr-xr-x  2 fog  root   4096 May 30 19:50 10secdelay
    -rw-r-xr-x  1 fog  root    868 May 30 19:50 boot.txt
    -rw-r--r--  1 root root    426 May 30 19:51 default.ipxe
    drwxr-xr-x  2 fog  root   4096 May 30 19:50 i386-7156-efi
    drwxr-xr-x  2 fog  root   4096 May 30 19:50 i386-efi
    -rw-r-xr-x  1 fog  root 199200 May 30 19:50 intel7156.efi
    -rw-r-xr-x  1 fog  root 226624 May 30 19:50 intel.efi
    -rw-r-xr-x  1 fog  root  95712 May 30 19:50 intel.kkpxe
    -rw-r-xr-x  1 fog  root  95760 May 30 19:50 intel.kpxe
    -rw-r-xr-x  1 fog  root  95763 May 30 19:50 intel.pxe
    -rw-r-xr-x  1 fog  root 942112 May 30 19:50 ipxe7156.efi
    -rw-r-xr-x  1 fog  root 994048 May 30 19:50 ipxe.efi
    -rw-r-xr-x  1 fog  root 870400 May 30 19:50 ipxe.iso
    -rw-r-xr-x  1 fog  root 349096 May 30 19:50 ipxe.kkpxe
    -rw-r-xr-x  1 fog  root 349144 May 30 19:50 ipxe.kpxe
    -rw-r-xr-x  1 fog  root 348333 May 30 19:50 ipxe.krn
    -rw-r-xr-x  1 fog  root 348913 May 30 19:50 ipxe.pxe
    -rw-r-xr-x  1 fog  root 123448 May 30 19:50 ldlinux.c32
    -rw-r-xr-x  1 fog  root 187820 May 30 19:50 libcom32.c32
    -rw-r-xr-x  1 fog  root  26468 May 30 19:50 libutil.c32
    -rw-r-xr-x  1 fog  root  26140 May 30 19:50 memdisk
    -rw-r-xr-x  1 fog  root  29208 May 30 19:50 menu.c32
    -rw-r-xr-x  1 fog  root  43186 May 30 19:50 pxelinux.0
    -rw-r-xr-x  1 fog  root  43210 May 30 19:50 pxelinux.0.old
    drwxr-xr-x  2 fog  root   4096 May 30 19:50 pxelinux.cfg
    -rw-r-xr-x  1 fog  root 199168 May 30 19:50 realtek7156.efi
    -rw-r-xr-x  1 fog  root 225984 May 30 19:50 realtek.efi
    -rw-r-xr-x  1 fog  root  96516 May 30 19:50 realtek.kkpxe
    -rw-r-xr-x  1 fog  root  96564 May 30 19:50 realtek.kpxe
    -rw-r-xr-x  1 fog  root  96611 May 30 19:50 realtek.pxe
    -rw-r-xr-x  1 fog  root 197984 May 30 19:50 snp7156.efi
    -rw-r-xr-x  1 fog  root 225056 May 30 19:50 snp.efi
    -rw-r-xr-x  1 fog  root 198176 May 30 19:50 snponly7156.efi
    -rw-r-xr-x  1 fog  root 225248 May 30 19:50 snponly.efi
    -rw-r-xr-x  1 fog  root  95300 May 30 19:50 undionly.kkpxe
    -rw-r-xr-x  1 fog  root  95348 May 30 19:50 undionly.kpxe
    -rw-r-xr-x  1 fog  root  95316 May 30 19:50 undionly.pxe
    -rw-r-xr-x  1 fog  root  29728 May 30 19:50 vesamenu.c32

  • Moderator

    @BiologyBen on the surface this looks like the target computer booted to the fog menu OK.

    I’m going to IM you since the turn around time on questions is faster. Look at the talk bubble on the FOG tool tray at the top of the browser window.

  • Moderator

    @BiologyBen looking at it now

  • @george1421

    Unfortunately, I get (Error - Invalid file type. Allowed types are: .png, .jpg, .bmp, .jpeg) whether I choose upload image or upload file.

  • Senior Developer

    @BiologyBen Maybe the TFTP boot files were not properly copied? What do you see when running ls -al /tftpboot on your FOG server?

  • Moderator

    @BiologyBen you should be able to upload, if not please copy it to a google drive or dropbox. Reading a pxe boot is an art more than skill.

    As far as you up load it looked like it completed.

  • @george1421 said in TFTP Boot File Not Found:

    if its running your output should look like this:
    [root@sfog03 bin]# netstat -an|grep 69
    udp 0 0*

    I get:

    udp        0      0    *                          
    udp        0      0 *                          
    udp6       0      0 :::69                   :::*                               
    udp6       0      0 :::51369                :::*    
    I get udp6       0      0 :::69                   :::*                               
    udp6       0      0 :::51369                :::*

    Which does have one line that matches yours 😉

    Working on the other - gedit wouldn’t open - here it is

    [0_1496768752259_output.pcap](Uploading 100%)
    – Oops - apparently I cannot upload this file type and it is obviously not a txt file - Installing wireshark…

  • @george1421 said in TFTP Boot File Not Found:

    When you installed fog did you answer no to using the dhcp server built into FOG?

    Right - I believe I answered no as I knew we had DHCP on the 2012 server.

    @george1421 said in TFTP Boot File Not Found:

    If fog and your pxe booting clients are on the same subnet

    Yes - They are.

    I’ll try to follow the guide and let you know.

  • Moderator

    To answer your question how to know if tftp is running on the fog server. The easiest way is to check to see if its listening on the tftp port.

    netstat -an |grep 69

    if its running your output should look like this:

    [root@sfog03 bin]# netstat -an|grep 69
    udp        0      0    *

  • Moderator

    @BiologyBen I’m thinking that your dhcp server isn’t configured correctly.

    When you installed fog did you answer no to using the dhcp server built into FOG?

    If fog and your pxe booting clients are on the same subnet (they are according to your IP addresses) then we can use the fog server to listen in on the dhcp setup of your pxe client. This is a bit techie, but I have a tutorial you can follow.

    The idea is that we will start the receiver on the FOG server then try to pxe boot the target computer. Do this until you get the error. Then stop the receiver (tcpdump) on the fog server and then upload the pcap here so we can review.