PXE Problems (random)

[Tom Elliott]

Does the DHCP server have the proper scope options specified (either Option 66 – IP of tftp server or next-server (and/or) Option 67/filename – undionly.kpxe)

[Jvdkruit]

i will check that out Tom… thanks

[Jaymes Driver]

With DNSMASQ you don’t need the DHCP on the server and you don’t need to adjust scopes. You supply all the information in the ltsp.conf file.

[Jvdkruit]

Jaymes… The PXE is also coming from another server… so… uhm… I feel myself a n00b right now…

[Jaymes Driver]

So your FOG server is not supplying your PXE or your boot menu?

[Jaymes Driver]

Could you give us a better understanding of your network and servers?

[Jvdkruit]

sure:
I have a DHCP Server: 192.168.50.1
And a PXE Server: 192.168.50.95
I’m now asking the network manager if i can get the pxe-settings, once i have that i will post it here!!

[Ahagel]

Hey John,

I am having the exact same issue when trying to upgrade my kernel to one of the latest versions. I also use our networks DHCP server that points to the FOG Server and Bootfile name undionly.kpxe. Though, I have no issues getting my machines to pxe boot into the FOG menus. Is there a known solution to this outside of using the FOG server for DHCP?

[Wayne Workman]

@Ahagel Can you type out (or post a photo of) the exact error?

Also, take a look at this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP

[Ahagel]

@Wayne-Workman Here you go. I will look at the TFTP troubleshooting steps as well. Thanks.

[Wayne Workman]

@Ahagel I’d recommend ensuring your FTP stuff is correct as well… https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

and perhaps reinstall FOG using the installer you have and see if your issues are resolved.

[Wayne Workman]

@Ahagel said:

Is there a known solution to this outside of using the FOG server for DHCP?

You can use Windows DHCP. You could even use ProxyDHCP (dnsmasq).

The TFTP article I posted links to those topics.