So it looks like I have resolved my DHCP problem with this host.

After looking over the post Sebastian Roth posted, I confirmed that we have the exact same model NIC and problem. Then while reading the post by george1421 regarding Spanning-Tree, I re-checked all switches in my imaging room. None of the ports on the switch at the host had spanning-tree portfast enabled. I left this off all ports in an effort to have as plain of configuration as possible.

I went ahead and enabled spanning-tree portfast on the port the host was connected to and re-tried FOG. This time it went right to the host registry and inventory process without stopping.

For now, it looks like I am back in business.

Thank you all for your assistance.

@george1421 I have two switches that I have confirmed have empty configurations with no spanning tree, switchpotrt
or VLAN information. I, also, disconnected the core switch from the rest of the network, after the target system obtained it’s initial DHCP address for PXE. We still had the same problem. Interface eth0 does not appear to be initializing and, if it is, it is unable to obtain a lease from the DHCP server.

I just realized that both switches may be missing their helper address information for DHCP. Could this be contributing to the problem?

@Tom-Elliott I checked the setting and it is /fog/

@coh_is So after documenting the iPXE error, I located another post on this forum with the same problem. In that post was a reply by you (george1421):

@george1421 said in IPXE Error: No configuration methods succeeded:

@Gary-Kulovics A screen shot of the actually error would be helpful to know exactly where in the process its failing.

What model of dell laptop are we talking about here?

The network port where this target computer is plugged in, do you have spanning tree enabled on that switch port, if you do are you using one of the fast spanning tree protocols (port-fast, fast-stp, rstp, [or the other one I can’t remember immediately])?

If you place once of those small unmanaged “cheapie” switches between the building switch and the target computer does it boot correctly?

If your target computer is in bios (legacy) mode then you will want undionly-(k)kpxe. That has worked on every dell device I have in my fleet.

I used the information in the last line of you post to change the dhcp bootfile name to undionly.kkpxe from undionly.kpxe and retried. Now I am able to get past this initial problem and to the FOG menu, but now I have a new one.

After selecting either of the host registry and inventory options, it looks like FOG is unable initialize DHCP and get an address. I fired up Wireshark on another system and did not see any additional DHCP requests coming from this target system. I did, however, see the initial DHCP request iPXE had made when it received an IP address from the DHCP server.

Headed back to the drawing board.

Upon initial PXE connection the computer did receive an IP address, but the process terminated with the following message on the iPXE screen:

Configuring (net0 <mac address>)…No configuration methods succeeded (http://ipxe.org/040ee119).

I checked this link and will be looking over the information provided.

However, prior to upgrading Ubuntu to 16 and FOG to 1.4.4, we were on the Ubuntu 14 and FOG 1.2, and were receiving the same error message as the OP in this post: https://forums.fogproject.org/topic/10104/compatibility-optiplex-7050-test-network-fail

I was having the same problem and I have done the following in an attempt to resolve it.

Upgraded Ubuntu to 16.0.4
Upgraded FOG to 1.4.4
Current Kernel is 4.11.0

PXE boot on Dell OptiPlex 7050 fails on configuring DHCP.

Dell has a walkthrough article on their site (http://www.dell.com/support/article/us/en/19/sln301475/fog-imaging-walkthrough?lang=en) that I’m going to try next, but thought I would update this existing post with continued problems under current software.

Also, during the FOG upgrade, the config.class.php file had the MySQL password enclosed in double quotes, which MySQL doesn’t like, apparently. Changing to single quotes and reloading apache2 (service apache2 reload) resolved the problem and allowed me to continue with the FOG install/upgrade.