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

    Lenovo (m)70e tftp problem

    Scheduled Pinned Locked Moved
    Hardware Compatibility
    3
    7
    1.3k
    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.
    • R
      rb3314
      last edited by

      I have an older model Lenovo desktop with a Marvel Yukon Nic
      It is showing Yukon PXE v6.62.1.3 Pre Boot v2.1

      During the PXE boot it is giving an error:
      PXE-T01: File not Found
      PXE-E3B: TFTP Error - File Not Found

      The best lead I have found is that a tcpdump shows the tftp file name with garbage

      the dump shows
      tftp: [udp sum ok] 31 RRQ “undionly.kpxeM-^?” octet size 0

      for many other models and brands of laptops that work just fine that same dump shows
      tftp: [udp sum ok] 31 RRQ “undionly.kpxe” octet size 0

      Is there some manipulation that can be done to the DHCP helper (options 66 & 67) or anything in tftp settings that might help that brand/version of Nic properly connect?

      Wayne WorkmanW george1421G 2 Replies Last reply Reply Quote 0
      • Wayne WorkmanW
        Wayne Workman @rb3314
        last edited by

        @rb3314 said in Lenovo (m)70e tftp problem:

        During the PXE boot it is giving an error:
        PXE-T01: File not Found
        PXE-E3B: TFTP Error - File Not Found
        The best lead I have found is that a tcpdump shows the tftp file name with garbage

        More importantly, what IP address is the request going to? Is it even correct? Also, what’s doing your DHCP?

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
        Daily Clean Installation Results:
        https://fogtesting.fogproject.us/
        FOG Reporting:
        https://fog-external-reporting-results.fogproject.us/

        1 Reply Last reply Reply Quote 0
        • R
          rb3314
          last edited by

          The IP address for TFTP is to our CentOS7 server running FOG, DHCP is handled by the Cisco Switch. There are no hops in between it and the switch.

          R 1 Reply Last reply Reply Quote 0
          • R
            rb3314 @rb3314
            last edited by

            Also, This same Lenovo model alternatively comes with a Realtek Nic which Pxe boots just fine.

            Wayne WorkmanW 1 Reply Last reply Reply Quote 0
            • Wayne WorkmanW
              Wayne Workman @rb3314
              last edited by Wayne Workman

              @rb3314 in the TCP dump, where the box gets a DHCP lease, what does DHCP give to it for option 067? We know the box is requesting the wrong filename. I’m wondering if DHCP is giving the correct file name.

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
              Daily Clean Installation Results:
              https://fogtesting.fogproject.us/
              FOG Reporting:
              https://fog-external-reporting-results.fogproject.us/

              1 Reply Last reply Reply Quote 0
              • george1421G
                george1421 Moderator @rb3314
                last edited by george1421

                @rb3314 said in Lenovo (m)70e tftp problem:

                the dump shows
                tftp: [udp sum ok] 31 RRQ “undionly.kpxeM-^?” octet size 0
                for many other models and brands of laptops that work just fine that same dump shows
                tftp: [udp sum ok] 31 RRQ “undionly.kpxe” octet size 0

                I’ve seen this before. If you look at the tcpdump hex codes (or wireshark). after the e in .kpxe the next byte needs to be 0x00 (end of string). There is also (at the beginning of the) undionly.kpxe the hex byte just to the left of the u is the number of bytes in that dhcp string.

                Ok with all of that said, there are some pxe boot roms that honor the byte count other boot rooms look for the 0x00 (end of text string) byte. If you look at the hex codes for “undionly.kpxeM-^?”, you will probably find a 0x00 after the question mark.

                So what can you do? Well this is a dhcp server / pxe boot rom issue (be aware this ISN’T a Fog issue). You need to change one of the two to be happy. You probably need to correct your dhcp server so it sends the end of text string. Certain flavors of ISC-DHCP have this same issue.

                If you can’t fix your dhcp server, then if needed you can use the dnsmasq on the FOG server to supply the pxe boot info, where your main dhcp server would handle the dhcp IP assignments only.

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                R 1 Reply Last reply Reply Quote 1
                • R
                  rb3314 @george1421
                  last edited by

                  @george1421

                  Thank you for the insight. Let me look at those items a little further.

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

                  162

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project