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

PXE-E53: No Boot File Received

Scheduled Pinned Locked Moved
FOG Problems
4
15
4.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.
  • J
    jamcdonald120 @Raymond Bell
    last edited by Feb 2, 2017, 8:25 PM

    there may be another DHCP server on the network, I don’t know, basically I have a room of 26 computers (one of which is the fog server) that I control all networked through a switch that I don’t control, that I dont know for sure, but I think that switch is running a DHCP server

    1 Reply Last reply Reply Quote 0
    • S
      Sebastian Roth Moderator
      last edited by Feb 2, 2017, 8:33 PM

      Well, you cannot really use FOG without knowing at least a little bit about DHCP and PXE and how this stuff is setup within your network. We won’t be able to help you as we don’t have any information.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      1 Reply Last reply Reply Quote 1
      • J
        jamcdonald120 @Sebastian Roth
        last edited by jamcdonald120 Feb 2, 2017, 2:35 PM Feb 2, 2017, 8:34 PM

        @Sebastian-Roth both are running, I have previously been able to use this install to image on this network, and I dont think it has changed since then

        R 1 Reply Last reply Feb 2, 2017, 8:38 PM Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by Feb 2, 2017, 8:35 PM

          https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_TFTP

          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          J 1 Reply Last reply Feb 7, 2017, 9:24 PM Reply Quote 0
          • R
            Raymond Bell Testers @jamcdonald120
            last edited by Feb 2, 2017, 8:38 PM

            @jamcdonald120 You have to add setting to the DHCP server to get fog to work… If you do not have access to this then you will not be able to use fog like Sebastian said. Look at the link he just posted.
            If you do have access to the dhcp server then we might be able to help you out.

            Raymond Bell
            WiKi: https://wiki.fogproject.org/wiki/index.php/Main_Page

            Q 1 Reply Last reply Feb 3, 2017, 2:37 PM Reply Quote 0
            • Q
              Quazz Moderator @Raymond Bell
              last edited by Quazz Feb 3, 2017, 8:37 AM Feb 3, 2017, 2:37 PM

              @Raymond-Bell If he does not have access to DHCP server, he could actually use dnsmasq DHCP proxy for handing out boot files.

              https://wiki.fogproject.org/wiki/index.php?title=Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server

              R 1 Reply Last reply Feb 3, 2017, 4:35 PM Reply Quote 1
              • R
                Raymond Bell Testers @Quazz
                last edited by Feb 3, 2017, 4:35 PM

                @Quazz True forgot about that.

                Raymond Bell
                WiKi: https://wiki.fogproject.org/wiki/index.php/Main_Page

                1 Reply Last reply Reply Quote 0
                • J
                  jamcdonald120
                  last edited by Feb 7, 2017, 7:51 PM

                  if we assume that the DHCP setting of the router are correct (they worked before) is there anything else that could cause the problem?

                  1 Reply Last reply Reply Quote 0
                  • J
                    jamcdonald120 @Sebastian Roth
                    last edited by Feb 7, 2017, 9:24 PM

                    @Sebastian-Roth I am able to run the tftp -v x.x.x.x -m binary -c get undionly.kpxe command from the machine I am trying to image, it worked. but pxe still reports no boot file recieved

                    1 Reply Last reply Reply Quote 0
                    • S
                      Sebastian Roth Moderator
                      last edited by Sebastian Roth Feb 8, 2017, 3:43 AM Feb 8, 2017, 9:25 AM

                      @jamcdonald120 said:

                      if we assume that the DHCP setting of the router are correct (they worked before) …

                      I am sure I have heard phrases like this more than a hundred times and it quite often turns out …

                      Asking the web to see what other things could cause this issue I see that the error message you posted is not quite the same most other people report - which is: PXE-E53: No boot Filename received (see the difference between ‘File’ and ‘Filename’?). Your positive test of trying to load the undionly.kpxe (how do you know your server is using this file and not ipxe.kpxe which we also use sometimes?) binary file makes me believe that your TFTP and the files on it are fine. This would emphasize even more that something is wrong with the DHCP! The message essentially says: “I got an answer from a DHCP server but no information on what file to load for PXE booting”.

                      You need to understand that DHCP is always a bit of an issue. This is because even if neither you nor any colleague changed the “original” DHCP server you can still run into problems if someone added another DHCP server answering requests in your network.

                      Please try this: Make one of your clients ready for turn on and PXE boot. Install and run tcpdump - a tool to capture network traffic - on your FOG server.

                      sudo -i
                      apt-get install tcpdump
                      tcpdump -w /tmp/dhcp_traffic.pcap port 67 or port 68 or port 69 or port 4111
                      

                      Leave that command as is and start up the client till you see the error message on screen. Then stop the tcpdump command (Ctrl-c) and upload that packet dump file (/tmp/dhcp_traffic.pcap) from your server to the forum here.

                      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

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

                      186

                      Online

                      12.1k

                      Users

                      17.3k

                      Topics

                      155.3k

                      Posts
                      Copyright © 2012-2024 FOG Project