with undionly.kkpxe - I get a reboot no messages
with undionly.kpxe - I get a reboot no messages
with undionly.kpxe.INTEL - I get a fog menu. I did a host registration on and older PC and it worked, on the newer PC it doesn’t work.
with ipxe.kpxe I get a fog menu - same error as the .INTEL file
with ipxe.kkpxe I get a fog menu and again same error.

The error is DHCP/BOOTP: Reply not for us, op[2] xid[number changes] repeats this with different xid numbers then says:
IP-Config: Reopening network devices…
repeats again with different xid numbers.

should I try using an older version of fog?

[quote=“x106, post: 35109, member: 25501”]I’ve only tried the .kpxe file, not kkpxe so I’ll try that and get back.[/quote]

[url]http://ipxe.org/1d8c2139[/url]

This is the error the kkpxe comes up with.

I’ve only tried the .kpxe file, not kkpxe so I’ll try that and get back.

I think I’m making headway but now may be having a different problem with the new PXE.

I’m getting the FOG menu on one test computer which is the primary model I’ve imaged with the old .32 server HP DC5800 but on older HP DX5150 MT I’m getting a message that says press enter to restart or something to that effect. I’m guessing there is an issue with this NIC or PC loading this PXE?

I will do so today, thanks

I can do the same thing on another ethernet port if you like, without the delay. That port is one I use to test my access points so there is some extra configuration to allow the access points to tag my other VLANs that are accessible on that port. [I]Edit:[/I] I do have 3 other ports without that VLAN configuration in my office to test with, I thought I should explain this better. The access points are configured to use my normal data VLAN for their configuration and those ports the access points use also have access to my other VLANs. When I use a PC on that port they don’t immediately get an address - it seems to take some amount of time before they use the default VLAN specified on that port.

I assure you that the DHCP delay is not related to this problem.

[media=youtube]SFLGEST32GI[/media]

I’m still having the same problem with Debian. I recorded a video that hopefully, will help.

I can imagine recommending against it with all of the similar issues I’ve been reading. It sounds like there are so many reasons PXE could not be working that it goes from very simple OS or firmware issues to possibly more complicated switch issues.

I’m definitely trying Debian right now, it would be nice if it was just that easy.

I just installed fresh while waiting for replies and I’m PXE seems to load but slow. I believe there is an error message on the first screen then it goes to an iPXE screen that says configuring and lists the NIC’s MAC address, I’m assuming. Then when it slowly gets past that the system reboots. I don’t have to use VMware, but it is definitely easier to test that way.

When the installation video listed on the site goes through all the steps in Ubuntu it genuinely seems like it is being supported. I’ll try Debian though.