Bug #2870
closed
DHCP reservations on MS DHCP servers with PXEClient defined
Description
On our internal MS DHCP servers PXEClient is set to PXEClient (probably pretty common). This makes from what I understand make the pxe boot rom try to contact the dhcp server on port 4011 to obtain the boot file. This fails and the machine will not pxe boot.
http://www.sempersoftware.com/what-option-60
http://www.experts-exchange.com/Networking/Misc/A_2978-PXEClient-what-is-it-for-Can-I-use-PXE-without-it.html
I have created a pull request which tries to mitigate this issue by setting option 60 to empty string for the reservation.
Updated by Dominic Cleal over 11 years ago
- Project changed from Foreman to Smart Proxy
- Category set to DHCP
- Status changed from New to Ready For Testing
- Target version set to 1.3.0
Updated by Tomas Edwardsson about 11 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 296617acd29db1759cc5b5bfffad39398e3773a4.
Updated by Oliver Weinmann over 10 years ago
Hi Guys,
I opened a ticket for another MS dhcp issue: http://projects.theforeman.org/issues/5995. It seems that this fix broke my ms dhcp configuration. On my MS Dhcp Windows 2008 R2 there is no option 60. Since the option doesn't exist, the smart proxy was failing to create the dhcp entry. Can you maybe change the code so that the option is only set if available?
Updated by Dominic Cleal over 10 years ago
- Related to Bug #5995: Windows AD DHCP reservation creation fails with "The specified option does not exist" added