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

    boot uefi don't work

    Scheduled Pinned Locked Moved
    FOG Problems
    4
    25
    4.6k
    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.
    • george1421G
      george1421 Moderator @pascald73
      last edited by

      @pascald73 While I haven’t been following this thread, it appears you missed arch 007 EFI BC. Typically for intel based computers it going to be type 009 EFI x64 or 007 EFI BC.

      If setting that still doesn’t work then we can look into what is flowing down your network.

      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!

      P 1 Reply Last reply Reply Quote 0
      • P
        pascald73
        last edited by

        I made a video to be able to read the error message that doesn’t even last 1 second.

        server ip adresse is : my ip AD server
        NBP filename is ipxe.efi
        NBP filesize is 0 Bytes
        PXE-E99: unexpected network error.

        it’s only on the new laptops.
        on my old machines the fog server works fine

        george1421G 2 Replies Last reply Reply Quote 0
        • george1421G
          george1421 Moderator @pascald73
          last edited by

          @pascald73 Is your FOG server and pxe booting computer on the same subnet?

          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!

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

            @pascald73 said in boot uefi don't work:

            server ip adresse is : my ip AD server

            Just looking at this, because I think that should be the IP address of the FOG server. What do you have set for dhcp option 66?

            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!

            P 1 Reply Last reply Reply Quote 0
            • P
              pascald73 @george1421
              last edited by pascald73

              @george1421
              i set my fog server ip in option 66

              1 Reply Last reply Reply Quote 0
              • P
                pascald73 @george1421
                last edited by

                @george1421
                I did not see the option arch 67 efi BC
                can you tell me more about how to set this one up?
                Thanks in advance

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

                  @pascald73 In your picture it shows (guess) that you set arch 009 008 006 but you missed 007.

                  Also for each dhcp policy you defined a new dhcp option 66. You can safely remove that extra value because with the policy the dhcp value 66 is not changed from the global value.

                  So you will setup global dhcp options within the scope
                  66 IP address of FOG server
                  67 undionly.kpxe

                  Then for your dhcp polices only set dhcp option 67

                  Now that you changed the dhcp option 66 to the FOG server IP address what error do you get now?

                  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!

                  P 1 Reply Last reply Reply Quote 0
                  • P
                    pascald73 @george1421
                    last edited by

                    @george1421
                    Also for each dhcp policy you defined a new dhcp option 66. You can safely remove that extra value because with the policy the dhcp value 66 is not changed from the global value.

                    So you will setup global dhcp options within the scope
                    66 IP address of FOG server
                    67 undionly.kpxe

                    Then for your dhcp polices only set dhcp option 67

                    Now that you changed the dhcp option 66 to the FOG server IP address what error do you get now?

                    i have is error:
                    server ip adresse is : my ip AD server
                    NBP filename is ipxe.efi
                    NBP filesize is 0 Bytes
                    PXE-E99: unexpected network error.

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

                      @pascald73 Is your FOG server and pxe booting computer on the same network subnet?

                      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!

                      P 1 Reply Last reply Reply Quote 0
                      • P
                        pascald73 @george1421
                        last edited by

                        @george1421
                        my fog server ip is in 172.16.0
                        and the scope of computer in 172.16.2. range

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

                          @pascald73 So yes or no target computer is on the same subnet as the FOG server? You tell me IP address but not subnet mask to answer the question.

                          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!

                          P 1 Reply Last reply Reply Quote 0
                          • P
                            pascald73 @george1421
                            last edited by

                            @george1421 said in boot uefi don't work:

                            o yes or no target computer is on the same subnet as the FOG server? You tell me IP address but not subnet mask to answer the question.
                            sorry, submask is 255.255.0.0

                            george1421G 1 Reply Last reply Reply Quote 0
                            • P
                              pascald73
                              last edited by

                              i try the option 60 pxeclient.
                              i have another error

                              error
                              PXE-E16: No offer received

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

                                @pascald73 OK so the answer is yes they are on the same IP subnet. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

                                Follow those instructions to create a network pcap (packet capture). Upload the pcap to a file share site and either post the link here or send me a Private Message with a link to the pcap and I will look at it and tell you what is wrong.

                                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!

                                P 2 Replies Last reply Reply Quote 0
                                • P
                                  pascald73 @george1421
                                  last edited by

                                  @george1421
                                  i have tcdump port 67
                                  but i’m totaly newbie in linux.
                                  i don’t kwon to send you the cap

                                  1 Reply Last reply Reply Quote 0
                                  • P
                                    pascald73 @george1421
                                    last edited by

                                    @george1421
                                    hello
                                    I sent the files by link in private message
                                    thank you for your help

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

                                      @pascald73 based on your pcap I think you have your dhcp server configured like this, which is wrong because you did not define dhcp option 66. Understand this is only a guess based on what I see.

                                      scope_settings2.png

                                      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!

                                      P 1 Reply Last reply Reply Quote 0
                                      • P
                                        pascald73 @george1421
                                        last edited by

                                        @george1421
                                        hello george
                                        i have set this for a long time with my fog server 1.2.0
                                        my image capture
                                        fog1.jpg

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

                                          @pascald73 Ok I see the problem. You need to remove (uncheck) the dhcp option 66 values in each policy. Make sure this is unchecked in your policy

                                          policy2.png

                                          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!

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

                                            @george1421 When you have your policies configured correctly they will look like this.

                                            policy3.png

                                            You see only one value is set in each policy and that is dhcp option 67. The dhcp option 66 is only set at the scope level because that does not need to change between different types of booting computes.

                                            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!

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

                                            157

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project