How to get windows 2008server r2 DHCP to hand out an IP to a PXE-booting client

dhcppxe-bootwindows-server-2008-r2

I really need some help here, Im trying to get a client to PXE-boot using WDS from a 2008 server R2. I've set up a DHCP scope from

10.0.0.11 – 10.0.0.20
255.255.255.0

The server is handing out IPs to the client when it's booted up, but when it's booting it searches for DHCP, and after about 45sec it returns "No DHCP or proxyDHCP offers were recieved"

The WDS-role is set up to accept any client, but i've also added the client to computers in AD based on the GUID.

The NIC on the client is Broadcom netxtreme 1.

Any clues to what i am doing wrong would be greately appriciated.

Best Answer

A regular DHCP server only provides an IP, a mask, and some other DHCP options. a PXE enabled DHCP server additionally provides the IP address of the TFTP server and the name of the first file to retrieve by a net booting station (NBP=Net boot program) If you already are using Microsoft's DHCP server you have to configure it to hand out information needed for PXE booting by ticking the appropriate WDS configuration checkboxes:

enter image description here

Related Solutions

Linux – PXE Boot – Linux server & OpenBSD client

The 1st thing I've spotted was that you are using "-s /tftpboot" in xinetd.conf and adding the dhcpd.conf "root-path" option. Setting the "-s" option for tftpd means that is the "/" directory as seen for tftp client. So your dhcpd.conf should only have "filname /pxeboot", without the root-path option.

From "man tftpd":

-s

Change root directory on startup. This means the remote host does not need 
to pass along the directory as part of the transfer, and may add security.
When -s is specified, exactly one directory should be specified on the command
line. The use of this option is recommended for security as well as compatibility
with some boot ROMs which cannot be easily made to include a directory name 
in its request.

How to get Windows Server 2003 DHCP to hand out the newly-expanded Subnet Mask

Changing the subnet mask of a scope isn't possible. If you don't have a lot of reservations the simple solution would be to simply create a new scope and disable the old one.

Update, here is an howto that describes how to export/import reservations. I haven't tried this myself though.

Best Answer

Related Solutions

Linux – PXE Boot – Linux server & OpenBSD client

How to get Windows Server 2003 DHCP to hand out the newly-expanded Subnet Mask

Related Topic