Setting Option 66 and 67 for DHCP

Updated: April 4, 2016 | 10 comments | Tags: , , , ,

To get PXE working on a server that is running both DHCP and WDS you need to enable option 66 and 67.
These settings will help your connecting clients to find the appropriate PXE server.

The setting is found in the DHCP configuration manager window (MMC).

Expand IPv4 and go to Server Options, right-click and select Configure Options.
Scroll down and select:

066 Boot Server Host Name
067 Bootfile Name

For option 066 write the IP of your WDS server. (10.0.0.150 for example).
For option 067 write: \smsboot\x64\wdsnbp.com

Press OK and try booting the client.

If you’re getting any error messages regarding PXE please read this article!

Let us know if you run into any problems!

10 Comments

  1. ugg on 2012-10-05 at 14:47

    Thanks for sharing this, great :)

    Reply
  2. well l on 2012-10-10 at 00:15

    THX for sharing.

    Reply
  3. Chad on 2013-10-14 at 19:50

    Thanks so much. Been banging my head against a wall for hours trying to figure this out.

    Reply
  5. Matt on 2015-08-05 at 13:24

    I am using Hyper-v In a test lab.

    I have setup as above but get an error:

    NBP filename is \smsboot\x64\wdsnbp.com
    nbp filesize is 0 bytes

    pxe-e99 unexpected network error.
    Boot failed. EFI network.

    If you can assist, I would be very grateful, I am using WDS 2012 with SCCM 2012 R2.

    Thanks Matt

    Reply
    • Joakim on 2015-08-12 at 07:40

      Hi Matt,

      Are you running VLANs in your lab network? Is the client/guest Generation 1 or 2?

      Best regards,
      Joakim

      Reply
    • Dan Orozco on 2018-10-19 at 17:25

      Hi Matt, Im hoping you were able to resolve this years ago but I'm getting the exact error. I would really like to hear what solved your issue. Here is my output. It is clearly getting ready to download the right file from the right server….

      Server IP 10.10.1.104

      NBP filename is boot\x64\wdsmgfw.efi
      nbp filesize is 0 bytes

      PXE-E99 Unexpected Network Error

      Reply
      • Adrien on 2019-06-21 at 09:26

        Hello Dan, Joakim,

        I have the exact same issue (been working on it for 2 days now) and I have no idea what's going on.

        BIOS boots fine but UEFI doesnt.

        We have a deployment VLAN with WDS and clients, the dhcp is on another VLAN.
        We use ip-helpers.

        Any help would be greatly appreciated !

  6. Nick on 2016-05-19 at 09:36

    Hi, i'm still getting the PXE-E32: TFTP open timeout error
    I configured the options. Any advice?

    Reply
    • Joakim on 2016-05-19 at 11:32

      Hi Nick,

      The "PXE-E32" error indicates that the PXE client did not get a reply from the TFTP server when sending a request to download its boot file. Possible causes for this problem are:

      1. There is no TFTP server
      2. The TFTP server is not running
      3. TFTP and DHCP/BOOTP services are running on different machines, but the next-server (066) option was not specified

      Best regards,
      Joakim

      Reply

Trackbacks/Pingbacks

  1. DHCP Woes I actually think my head is going to explode - […] you have to point a network booting machine to the image server by setting DHCP options 66 and 67.…

Submit a Comment

Your email address will not be published. Required fields are marked *