Unsure what could have changed just recently… everything is suddenly working for the systems that we had issues with.

I re-applied the 13.14.4 kernel, and everything started functioning. I’ve tried to update the kernel with different versions that we had been trying, but they all seem to be working now as well. Maybe there was just a problem with the kernel when it was downloaded. At any rate, the issues seems to have gone away. If I run into this again, I’ll try to post what kernel we have installed and all relevant configuration information.

Single DHCP server. Everything except for imaging for a few systems works fine (iPXE menu loads, registration works, etc).

Integrated network adapter (Intel 82567LM-3 Gigabit)

Waiting doesn’t do anything. We let the system sit all night (12+hours) thinking it might just take a good while to initialize; no go.

Compatibility test is PASS for both Disk and Network.

Now, I’m not 100% sure what all of these files do, but here’s what we’ve tried updating / changing:
Tried undionly.kpxe that was included in the source install (93.3kb) as well as one fromsourceforge.net/p/freeghost/code/1312/tree/trunk/packages/tftp/ (98.1kb) - no change in behavior.
Tried kernel 13.14.2, 13.14.4 (both the TomElliot version, not Core); no change.

Tom, the issue seems to lie in imaging only.

The FOG server we set up was originally installed with version .32 on Ubuntu 10.04; we have since upgraded to version 1.0.1 on the same server. DHCP is served through Windows Server 2008 R2, options 66/67 are configured correctly. We are using the 3.14.2 kernel. With no tasks created, systems are loading the iPXE chain fine. Registration works fine. Once a task is submitted (either through registration or through the web GUI), the process fails.

After a lease is obtained, iPXE does its thing and we receive a screen as below:

[IMG]http://i1258.photobucket.com/albums/ii540/aepriest/fog1_zpsb43d6342.png[/IMG]

[IMG]http://i1258.photobucket.com/albums/ii540/aepriest/fog2_zps582d4601.png[/IMG]

Interestingly enough, this doesn’t happen for all hosts. We have a few virtual machines that we use for keeping our deployment images up to date, and they still FOG just fine. It is, however, not contained to just one set of hardware; there are a few different systems that do this.

I’ll check Apache, but everything seems to be served over http just fine.