@george1421 @Tom-Elliott
Luckily I could schedule a meeting with my System-Admin today, and he tried turning off the serving of the WDS boot file - seems in the configuration of option 66 and 67 of our companies DHCP server was an old Windows Server that served a meaningless WDS file, we changed it to my FOG Server and the issue is now solved.
I am very thankful for your first-class support and I apologize for the inconvenience! You guys are my heroes!
@george1421 said in UEFI: NBP downloaded successfully - then blackscreen:
This device may simply not be compatible with iPXE.
But this would also mean that I completely can’t PXE boot my device, however the whole thing works when doing it with legacy BIOS, so my educated guess would be that there is some problem with the NBP file that I am serving. Any suggestions?
Sadly USB boot is not suitable for my use case
Concerning the “stealing” part: I will ask a system admin to look into this, because actually we shouldn’t have any WDS in our network 
@george1421 Sorry for the spam today.
I figured, that the problem might be with the NBP file (that I am serving the wrong one), because it’s working just fine with legacy.
My dnsmasq config is the one that you have provided: https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server?_=1693476360006
If it’s any worth: the machine I am trying to network boot is a Zotac Zbox (and thus has it’s own little bios distro (looks that way))
@george1421 Additionally, I want to remind that the whole process works with legacy BIOS, just not with UEFI BIOS. So maybe there is the problem? (I already tried using .efi files)
@george1421 Okay that’s unfortunate, so you are telling me there is already another instance in the network trying/stealing my network boot? I have a real hard time here understanding this issue.
Do you have a concrete advice for me? I am a bit overwhelmed
PS. I tried network booting with a completely other device, and it was working. However, I primarily need the device to network boot that can’t do it.
@george1421 Yes it is. Both, the fog server and the host device, are in VirtualBox - and i get the error message.
But tbh if the problem doesn’t show up when deploying the whole system in my network, i can live with the error occurring in VB.
If it’s true that this only happens in VB and not on the actual network (and then Toms solution works), then this issue is resolved for me.
@george1421 You are right - there are multiple dhcp servers But I disabled the isc-dhcp-service on my FOG server so I am more but puzzled why this still acts as a dhcp server.
Also my System-Admin tells me that we do not have a WDS server so that puzzles me even more 
But here comes my newbie question: shouldn’t dnsmasq be able to handle this? Or is there any option for my case to get this right without changing anything about the dhcp servers?
@george1421 Secure boot was already disabled (I already stumbled across this solution) - still not different.
Hello there!
I recently deployed a FOG Server onto my network, which only worked for legacy-bios hosts.
When trying to network boot an UEFI device I first get the following screen:
Then blackscreen. And this repeats every few minutes.
I tried .efi files as boot files - did not work (or did I do anything wrong - I don’t know).
A possible solution would be this:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_ProxyDHCP_.28dnsmasq.29
but unfortunately I have to use dnsmasq as a DHCP proxy because there is an existing DHCP server in my network that I am not allowed to alter.
I am happy to provide ma dnsmasq conf (I am sorry - its a mess, suggestions for improvement desired) and a .pcap file (from the failed “connection” attempt) at this link:
https://github.com/gabrielzeit/fog-files.git
I would really appreciate the help!
Thanks!
@george1421 I am using dnsmasq version 2.86
I now adapted your recommended configuration, but the error still occurs after the automatic reboot.
Do I have to change the boot file too somewhere? Because as I can see there are a lot of boot file names in the config.
@Tom-Elliott
Thank you for your fast reply!
Unfortunately this did not work for me.
(Maybe because I am using dnsmasq as a proxy for dhcp? but I guess this cannot be the issue here)
This is my dnsmasq config, where I’m also setting the boot file, is this config correct? Or do I have to set the boot file elsewhere?
port=0
log-dhcp
tftp-root=/tftpboot
dhcp-boot=ipxe.pxe,10.0.2.15
dhcp-no-override
pxe-prompt=“Press F8 for boot menu”, 3
pxe-service=X86PC, “Boot from network”,undionly
dhcp-range=10.0.2.15,proxy
I am worried about the “pxe-service” line, because there still stands “undionly” but changing that makes my FOG Server “not-seeable” (my clients don’t go into the FOG menu and there is a TFTP Error shown).
Will your solution also work when the FOG server is deployed in my network? (outside of VBox)
Hi there!
I recently discovered FOG to be excellent for my use case (to deploy OS over network), and proceeded with trying it in Virtual Box - it worked wonderful. Except one problem that I stumbled apon, and despite much time spent on internet research, I could not figure out the solution.
I was able to get FOG running on a Server and I also am able to capture and deploy images - BUT ONLY if I manually reboot the machines. After every automatic reboot (e.g. after the host registration) I get to the same error:
I tried using dnsmasq - did not work.
I tried using dhcp (also FOG as dhcp server) - did not work.
Internet research suggests things like changing undionly.kkpxe to ipxe.kkpxe - did not work.
Because I really do not know much of how DHCP works or how to configure it correctly (and the problems seems to be with DHCP) I hoped someone could help me out here.
Thanks!