@Sebastian-Roth Sorted. Many thanks for your help!!

@Base2Nathan Good to hear you figured it out. You might wonder why the config George suggested doesn’t use option tftp-server-... and option bootfile-name at all. There are two places in DHCP packets where PXE boot information can be placed. One is DHCP options as you have used them. But there is also next-server and filename what are fields within the DHCP header information. Take a closer look at the wireshark dump…

@magikmw Glad to see you found and fixed this. It’s good to know you really know your way around in that network stuff. It’s very hard for us to diagnose and help out with that kind of things.

@mecsr Great. I’m glad you have it working. Just as a word of warning, don’t advanced past the 4.15.2 version of the kernel until you update FOG, and even then stick with 4.15.2 until the developers can dig into why 4.17.0 is acting slow.

Hi, yeah I’d understood what you were getting at. I’ve tested with a dumb switch in line at the client end and it worked first time. Many thanks for your help.

Hi once again! Our problem, as it stands today, is solved. We ended up trying to install the FOG server on the same subnet with the host machines, which worked. After that we tried putting the machine back on the subnet where all our VMs are located. That broke it. Later the network admin realized that during his configuration he accidentally left a space after the IP on option 66. After that was fixed things stated working out. So in the end what I was chasing was a typo. A big thanks to @george1421 for being as helpful as You could during the troubleshooting process. I am now happily deploying my Windows 10 images. :)

@fox134 Well lets hope you don’t have an ipxe.exe in there… The client gets its booting information from (the) dhcp responsible for assigning an ip address to the target computer. So if you want the target computer to use a different boot file then you might update dhcp options 67. Now with that said, from your OP you say that FOG is giving out the IP addresses on a dedicated imaging network. So if you want to change the boot file, you will need to edit the dhcp config file on your FOG server. To see what you config file looks like, you can review this example: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Example_1 You will see for arch 7 and 9 it calls out ipxe.efi. You can replace that with maybe snponly.efi or any of the other efi files. Then you must restart your dns server. On ubuntu you would issue the command sudo systemctl restart isc-dhcp-server to restart the service.

@george1421 You are an absolute legend George. It works now and I was able to PXE boot from my client PC and upload it to the Hosts screen. I can view it on the network and everything is working correctly. Thank you so much!

Just cross-linking this here: https://forums.fogproject.org/topic/10615/ipxe-booting-possibly-broken-on-os-x-sierra-update

@Tom-Elliott from the logs: 10/7/2016 10:32 AM PowerManagement On demand shutdown requested. An on-demand shutdown is always queued and not being cleared. We need a clear on-demand tasks button.

@Sebastian-Roth said: @Wayne-Workman I like the “Related_to_xyz” naming. Would suite other things as well I guess. Might wanna add this to the Knowledge Base which is linked on the main wiki page!? Done.

@Sebastian-Roth said in Impossible to boot on PXE......: Wireshark filter bootp && tftp is great for this This has been in the wiki for some time, here: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_TFTP

We have some Lenovos that are weird. Pull the power cable and patch cable, hit the power button a few times, plug everything back up and auto-magically those weird ones start working…