• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    PXE Booting & TFTP

    Scheduled Pinned Locked Moved
    FOG Problems
    2
    5
    2.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      bearmode
      last edited by

      Hi all,

      Trying to get a PC to PXE boot to the server but I get the error below:

      PXE-T01: The specified file was not found.
      PXE-E3B: TFTP Error - File Not Found.
      PXE-M0F: Exiting Broadcom PXE ROM.

      I have set the scope options on the subnet for my floor (66 and 67).

      Setting this up at work. We have a DHCP server. I’ve tried various combinations on the install (latest version) with Ubuntu desktop 12.10. Anyone know how I can get this working?

      Thank you!

      1 Reply Last reply Reply Quote 0
      • M
        moss
        last edited by

        Have you double checked option 67 to make sure the names specified correctly? pxelinux.0, using a zero not an O?

        1 Reply Last reply Reply Quote 0
        • B
          bearmode
          last edited by

          Hi Moss,

          It is indeed a zero.

          1 Reply Last reply Reply Quote 0
          • B
            bearmode
            last edited by

            Any other ideas? I have re-installed fog on Ubuntu 10.04 and still the same problem. I can retrieve the pxelinux.0 file if I tftp from the windows machine. I named the local acount as administrator on the Ubuntu machine as I read that calling it fog might be problematic.

            1 Reply Last reply Reply Quote 0
            • M
              moss
              last edited by

              Although it sounds like DHCP options are correct, it might be worth checking it using Wireshark on the client PC. If you filter the capture to ports 67 & 68 (UDP but it doesn’t matter if you capture both TCP and UDP), then perform an ipconfig /release, ipconfig /renew or simply disconnect/reconnect the network cable. Within the captured packets you should be able to see the DHCP options and that pretty rules out DHCP configuration issues.

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              • First post
                Last post

              216

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project