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

    I am getting DCHP/BootP: Reply not for us. Or PXE- E51 :no dhcp or proxyDHCP offers were recieved

    Scheduled Pinned Locked Moved
    FOG Problems
    7
    18
    9.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.
    • Oscar HillikerO
      Oscar Hilliker
      last edited by

      Fog has been acting odd since 1.0.1

      1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott
        last edited by

        [quote=“Oscar Hilliker, post: 28525, member: 24172”]Fog has been acting odd since 1.0.1[/quote]

        Care to elaborate?

        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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        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 0
        • Oscar HillikerO
          Oscar Hilliker
          last edited by

          Tom,
          Just referring to the issue we had with it in this thread. I was wondering when it is deploying fog says “invalid bios please report” where do we report bios or computer types?

          1 Reply Last reply Reply Quote 0
          • Tom ElliottT
            Tom Elliott
            last edited by

            [quote=“Oscar Hilliker, post: 28527, member: 24172”]Tom,
            Just referring to the issue we had with it in this thread. I was wondering when it is deploying fog says “invalid bios please report” where do we report bios or computer types?[/quote]

            Only when it’s deploying or during the sending inventory part? My guess is the dmidecode that’s trying to read the bios is reporting it can’t find the information. It isn’t something you should report to us, but rather to the software maintainers for dmidecode or report to the motherboard manufacturer if you feel it’s necessary. Most people can just ignore the message though.

            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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

            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 0
            • Roger SaffleR
              Roger Saffle
              last edited by

              Are you still seeing this? We are getting it too. Two identical PCs right next to each other. One will work fine, the other will get the “not for us” message.

              1 Reply Last reply Reply Quote 0
              • Oscar HillikerO
                Oscar Hilliker
                last edited by

                Roger, it took us several attempts to get fog to respond. Read Tom’s comment about options 66/67. Keep in mind that like Tom says if you have voip phone’s or anything using TFTP or DHCP server it will sometimes say “response not for us”. I noticed some computers have problems with iPXE, it’s not like the old PXE where you could fog just about anything. Check your TFTP settings on your fog server and sometimes updated the computer’s firmware helps.

                1 Reply Last reply Reply Quote 0
                • Roger SaffleR
                  Roger Saffle
                  last edited by

                  UPDATE: we found that if we pull the AC power and the network cable then plug them back in that the PCs image just fine.

                  1 Reply Last reply Reply Quote 0
                  • G
                    Greg Gaspard
                    last edited by

                    [quote=“Roger Saffle, post: 30483, member: 24521”]UPDATE: we found that if we pull the AC power and the network cable then plug them back in that the PCs image just fine.[/quote]

                    I still can’t believe this worked but it did!!

                    We were having issues imaging Dell Precision T3500’s. All other computers on the network FOG’ed just fine (with the exception of Dell Optiplex 3020’s but that’s another issue). While researching the 3500’s, I heard my coworker chuckle in the other cubicle. I asked what could make her laugh after fighting with these for days. She mentioned this fix and we went and tried it. Still feeling dumbfounded but the entire classroom is queued up and will be cloning overnight.

                    I really can’t believe this.

                    1 Reply Last reply Reply Quote 0
                    • W
                      Wolfbane8653 Developer
                      last edited by

                      Interesting.

                      You pulled both power and ethernet?

                      If you have this issue again could you try just pulling the ethernet cable? There may be a possibility an insertion of a dhcp reset could fix the issue. Maybe?

                      [B]Edit:[/B]
                      Note added to Dell [FONT=sans-serif][COLOR=#000000]Precision T3500 and linked it to your post.[/COLOR][/FONT]
                      [FONT=sans-serif][COLOR=#000000][url]http://fogproject.org/wiki/index.php/WorkingDevices#Computers[/url][/COLOR][/FONT]

                      1 Reply Last reply Reply Quote 0
                      • JunkhackerJ
                        Junkhacker Developer
                        last edited by

                        I’m guessing that it’s actually a case of the network card not initializing properly. it’s previous state was not being completely cleared on shutdown, but removing power cleared it.

                        signature:
                        Junkhacker
                        We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                        1 Reply Last reply Reply Quote 0
                        • W
                          Wolfbane8653 Developer
                          last edited by

                          Added to more multicasting troubleshooting.
                          [url]http://fogproject.org/wiki/index.php/Multicasting#Power_cycle_and_Ethernet[/url]

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

                          211

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project