Updating the ip helper tables

Hardware tested: Intel D865GLCL - Will not PXE boot in this configuration.

Random Via based system with Realtek 8139 NIC and PXE 1.1 build 082 - Will not PXEBoot in this configuration.

Using DHCP options 66 and 67 may cause the client to bypass this communication with the network boot server completely and therefore circumvent or ignore the network boot server’s settings regarding answering clients. Removing the options and modifying the IP Helper on the router did the trick.

Now every client seems to work just fine, including our MS Virtual Server clients.

updating the ip helper tables-14updating the ip helper tables-90updating the ip helper tables-39

Clients may bypass the network boot server’s answer settings.

DHCP server is configured to offer up options 60, 66, and 67: Option 60: "PXEClient" Option 66: "2k3-wds.domain.local" Option 67: "boot\x86\wdsnbp.com" Clients get the ever-popular "No response from Proxy DHCP server on port 4011" Running a packet sniffer on the DHCP server reveals the following: DHCP Offer packet: Client IP: 10.9.1.103 Next Server IP Address: 10.9.1.35 (Correct IP of WDS server) Relay Agent: 10.9.1.254 Server host name not given Boot file name "\boot\x86\wdsnbp.com" Option 60: Vendor Class Identifier "PXEClient" Option 67: Bootfile name "boot\x86\wdsnbp.com" I then see a packet from the client (10.9.1.103) trying to get the bootfile from the DHCP server on port 4011.

Of course the server isn't hosting the bootfile so eventually we get the error message.

It will add a slight increase in network traffic because your DHCP requests will also get sent to your WDS server but your WDS server will discard that traffic and only respond to the PXEclient request.

There are often problems with the configuration you have and using options 66 and 67.

Leave a Reply