PXE Boot Errors

[briancurry]

After everything setup and configured, clients can’t PXE boot to the FOG server/services. Get a boot error on the device

Here is a screen shot of the error.

Tried a lot of permissions on the Linux server
We setup the DHCP options on the Windows DHCP server.

Hopefully someone can point out something quick and easy that I missed.

[briancurry]

@sebastian-roth

I found a setting deep in the configuration options to increase the default value from what is was to 99.

[george1421]

@briancurry said in PXE Boot Errors:

Now the endpoint boots to what looks like the FOG imaging menu but then goes away after about 2 seconds.

There is a boot menu timeout that FOG has. The value is set in the FOG-Settings menus (sorry don’t remember off the top of my head). If you hit the up or down arrow within the 2 seconds you should be able to navigate the fog ipxe menu

[Sebastian Roth]

@briancurry said in PXE Boot Errors:

Now the endpoint boots to what looks like the FOG imaging menu but then goes away after about 2 seconds.

Can you take a picture of this? Not sure if I follow what you say here. Don’t think I’ve seen this before that the menu goes away after 2 seconds, usually it’s 8 or so by default.

[briancurry]

What a great reply, it wasn’t the complete answer but caused me to look deeper into the DHCP server and configuration. The PXE options has been set in the master scope section of the server. However, I entered the settings into the action scope for the V-Lan I was looking to boot from.

Now the endpoint boots to what looks like the FOG imaging menu but then goes away after about 2 seconds. Is there a timeout setting on the FOG server and if so where? Or something on my endpoint side in the BIOS possibly?

Thank you in advance!

[Sebastian Roth]

@briancurry Just guessing here but to me it looks like you are using an external DHCP server, provided by your network admins?! Just looks like to me from the IPs seen on the screen. So I am wondering who did set up the DHCP server to PXE boot clients? Are DHCP options 66 and 67 set correctly? Possibly there is a typo in the filename (option 67), maybe just a leading or tailing space character?!