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

    UEFI and windows 10

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    19
    3.9k
    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.
    • H
      Hammett131
      last edited by

      I started a new fog server for a company I started with. No issue booting with legacy boot but once I change option 67 to ipxe.efi and try to pxe boot UEFI it looks like it is trying to download something real quick then just moves on. Anyone else see this issue or know of a resolution? I have done a bunch of research around on this site and spiceworks.

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

        @hammett131 ok I see why it doesn’t boot.

        The device is saying its a uefi system (EF-BC type 7) but 10.0.2.1 is sending undionly.kpxe as the boot file name. The target computer promptly downloads the file and chokes on it. Its saying the next server is 10.0.2.122, which is your fog server?

        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!

        H 2 Replies Last reply Reply Quote 1
        • george1421G
          george1421 Moderator
          last edited by

          Check to see if you have an extra white space on either side of ipxe.efi. If all else fails follow these instructions and post the pcap to a google drive. Either post the link here or IM me directly and I’ll take a look at it to see where the pxe booting is going sideways.

          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!

          H 1 Reply Last reply Reply Quote 0
          • H
            Hammett131
            last edited by

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • H
              Hammett131 @george1421
              last edited by

              @george1421 Not seeing any instructions? I just double checked no white spaces. I am also using a sonicwall as my dhcp so I don’t know how this effects anything. Please bare with me I am pretty knew to this “techier” stuff.

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

                @hammett131 Well and I’m old and I forgot to paste the link in. I had the link in the copy buffer, but just failed to execute. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

                Since you are not using a standard dhcp server, make sure there isn’t a spot for bios and a different one for uefi mode devices. I know pfsense has unique spots for each boot 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!

                H 1 Reply Last reply Reply Quote 0
                • H
                  Hammett131 @george1421
                  last edited by

                  @george1421 Odd I just noticed when I boot legacy it worked even with ipxe.efi. I thought with an efi it couldn’t legacy pxe boot. And I will work on those steps might not get back to you till tomorrow! Thanks

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

                    @hammett131 That is odd. I can tell you a uefi system will not boot a bios based kernel, and the same way around. They are two different ach types. I think generating a pcap of the process is going to tell us really what is going down the wire. You may have an unexpected dhcp server helping you out.

                    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!

                    H 1 Reply Last reply Reply Quote 0
                    • H
                      Hammett131 @george1421
                      last edited by Hammett131

                      @george1421 Well I think I am clearly doing something wrong (think my brain is fried from this). After I hit ctrl c all I get is 6 packets captured and 6 packets received by filter, 0 packets dropped by kernel.

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

                        @hammett131 It should dump the output into a file you cited in the tcpdump command. 6 packets is about right for dhcp boot.

                        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 @Hammett131
                          last edited by

                          @hammett131 If you use this filter
                          tcpdump -w output.pcap port 67 or port 68 or port 69 or port 4011
                          it should create output.pcap in the current directory where you ran the tcpdump command.

                          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!

                          H 2 Replies Last reply Reply Quote 0
                          • H
                            Hammett131 @george1421
                            last edited by

                            This post is deleted!
                            1 Reply Last reply Reply Quote 0
                            • H
                              Hammett131 @george1421
                              last edited by

                              @george1421 Silly me…long day clearly.
                              https://drive.google.com/open?id=0B3KPegStLS26aXVURGJ2X3psVS1qOFI1Vk1RdzRQU09zOUg4

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

                                @hammett131 ok I see why it doesn’t boot.

                                The device is saying its a uefi system (EF-BC type 7) but 10.0.2.1 is sending undionly.kpxe as the boot file name. The target computer promptly downloads the file and chokes on it. Its saying the next server is 10.0.2.122, which is your fog server?

                                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!

                                H 2 Replies Last reply Reply Quote 1
                                • H
                                  Hammett131 @george1421
                                  last edited by

                                  @george1421 I downloaded wireshark to check it real quick. Saw that to… but my setting on my sonic wall is ipxe…hmmmm sounds like something over there. Thanks for the help maybe I’ll try restarting it.

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

                                    @hammett131 If you can’t get your sonicwall to cooperate you can install dnsmasq on the FOG server to dynamically supply the boot information while you still use the sonicwall for dhcp services. There are a number of ways to get things working in your environment.

                                    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 1
                                    • H
                                      Hammett131 @george1421
                                      last edited by

                                      @george1421 yes it is and I found where in the sonicwall it had undionly.kpxe. It is booting to fog as we speak! Thanks so much just needed another set of eyes!

                                      K 1 Reply Last reply Reply Quote 0
                                      • K
                                        KellyM @Hammett131
                                        last edited by

                                        @hammett131 Do you mind explaining where in your sonicwall you found it showing undionly.kpxe?
                                        I have the exact issue - I changed my option 67 to ipxe.efi, but my pcap shows undionly.kpxe is being requested. I’ve been beating my head against my desk all day trying to get this figured out. Any help would be greatly appreciated!

                                        K 1 Reply Last reply Reply Quote 0
                                        • K
                                          KellyM @KellyM
                                          last edited by

                                          I finally found it!
                                          For anyone else with this issue, check the advanced tab of your Dynamic Lease Scope in your DHCP settings.
                                          I found the answer here that included the screenshot to make it super clear: https://community.spiceworks.com/topic/1772601-pxe-booting-with-a-sonic-wall

                                          H 1 Reply Last reply Reply Quote 0
                                          • H
                                            Hammett131 @KellyM
                                            last edited by

                                            @kellym Sorry I didn’t check the forums yesterday, glad you found it!

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

                                            183

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project