HP Elitebook 840 G6 - UEFI PXE Boot not working.
-
@DeRo93 Maybe different UEFI architectures than what your other machines are using
(Example)NOTE: There are many other UEFI architectures besides just “PXEClient:Arch:00007”.“PXEClient:Arch:00002” and “PXEClient:Arch:00006” both should get “i386-efi/ipxe.efi” as their option 067 boot file.
“PXEClient:Arch:00008”, “PXEClient:Arch:00009”, and “PXEClient:Arch:00007” should get “ipxe.efi” as their option 067 boot file.
“PXEClient:Arch:00007:UNDI:003016” should get “ipxe7156.efi” this file is specific to the Surface Pro 4.
-
@David-Osinski said in HP Elitebook 840 G6 - UEFI PXE Boot not working.:
@DeRo93 Maybe different UEFI architectures than what your other machines are using
(Example)NOTE: There are many other UEFI architectures besides just “PXEClient:Arch:00007”.“PXEClient:Arch:00002” and “PXEClient:Arch:00006” both should get “i386-efi/ipxe.efi” as their option 067 boot file.
“PXEClient:Arch:00008”, “PXEClient:Arch:00009”, and “PXEClient:Arch:00007” should get “ipxe.efi” as their option 067 boot file.
“PXEClient:Arch:00007:UNDI:003016” should get “ipxe7156.efi” this file is specific to the Surface Pro 4.
I tried every filename as 067 Bootfile Name. But still only beeping and back to Startmenu.
-
@DeRo93 So if you ignore the filters for a moment and go back to the main scope the default value for dhcp option 67 is undionly right? What happens if you just change that to ipxe.efi. Understand this is only a test and changing this WILL break bios boots. But we need to understand if its the boot file that is having a problem or your filters. Forcing the boot file to ipxe.efi will give you a direction to look.
beeping and back to Startmenu
Also can you explain this? What startmenu? Is it the firmware boot options menu or is it the FOG iPXE menu?
-
@george1421 said in HP Elitebook 840 G6 - UEFI PXE Boot not working.:
@DeRo93 So if you ignore the filters for a moment and go back to the main scope the default value for dhcp option 67 is undionly right? What happens if you just change that to ipxe.efi. Understand this is only a test and changing this WILL break bios boots. But we need to understand if its the boot file that is having a problem or your filters. Forcing the boot file to ipxe.efi will give you a direction to look.
beeping and back to Startmenu
Also can you explain this? What startmenu? Is it the firmware boot options menu or is it the FOG iPXE menu?
I dont even work with Filters. I have a Scope for FOG in DHCP on Windows Server 2019. Scope Options > 067 Bootfile Name is ipxe.efi atm. If i know i need to install a legacy image i just switch it to undionly.kpxe . Worked for years…
When i boot the HP i press F12 to boot from Network. After F12 i can select IPv4 or IPv6. I choose IPv4. Then Blackscreen with “Start PXE over IPv4”, after that the HP beeps and I see UEFI Startmenu where i can select if i want to boot to UEFI Setup or again Network Boot or Firmware update etc. …
-
@DeRo93 said in HP Elitebook 840 G6 - UEFI PXE Boot not working.:
When i boot the HP i press F12 to boot from Network. After F12 i can select IPv4 or IPv6. I choose IPv4. Then Blackscreen with “Start PXE over IPv4”, after that the HP beeps and I see UEFI Startmenu where i can select if i want to boot to UEFI Setup or again Network Boot or Firmware update
Ok now we have an idea where its failing now we need to understand why. Please follow this tutorial to create a pcap of the pxe booting process from the fog servers perspective. This pcap will provide the best quality information if the pxe booting computer and the fog server are on the same IP subnet. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
Upload the pcap to this thread, or a file share site and either post the link here or IM me the link. I’ll take a look at the pcap to see what is or isn’t working.
-
You’ll have to disable secure boot in BIOS.
-
@Quazz said in HP Elitebook 840 G6 - UEFI PXE Boot not working.:
You’ll have to disable secure boot in BIOS.
Did you read my first post? I already mentioned that I disabled Secure Boot in BIOS.
-
@george1421 Here is the PCAP File.
I also inspected the File with WireShark. I clearly see that the Notebook tries to download Undionly.kpxe. Why is he doing that? 067 Bootfile Name is set on ipxe.efi
-
I now checked the same process with a Lenovo Notebook. PCAP shows that he is downloading the correct file: ipxe.efi
-
Okay i GOT IT!
I noticed that my HP is getting Information from the replicated DHCP Server. Replication was not completed and there was undionly.kpxe instead of ipxe.efi. Changed the String and now its working!!! Thank you for your help!
-
@DeRo93 I’m glad you have it worked out. As you see in the pcap you are getting two offers from two different dhcp servers (13.252 and 13.253). Each one is giving a different boot file name. So based on random selection some systems should pxe boot correctly and others not. I’ve seen this in the past and know where to look. But its great you found it to add the knowledge to your tool box. Using wireshark/tcpdump is the only way to find this kind of problem, well done!
-
@DeRo93 said in HP Elitebook 840 G6 - UEFI PXE Boot not working.:
Elitebook
Same network segment for both PCs ?
I had an issue with UEFI with non-standard netmasking and after weeks of messing around with it learned that the I needed to have the broadcast address of 255.255.255.255 instead of the what should have worked (only on the router - router was a Cisco). Basically I use to hardwire in the correct broadcast address on the appropriate Cisco interface, I took that out (let the Cisco set up the default) and it worked… Don’t ask me why, it was “legal” from a networking perspective.
