6

DHCP Server Not Offering to PXE Client

BACKGROUND:

I'm in the process of adding PXE services to an existing SCCM 2007 server. The SCCM server is separate from the DHCP server (Server 2008 x86) and did not have PXE services or WDS installed. I added PXE services in the Config Manager before adding WDS as a role. Because DHCP is on a separate server, I did not make any changes to DHCP Options (there is not a current 60, 66, or 67 configured).

The WDS is configured with both a boot image (ripped from the Win7 install dvd and an install image which was created by someone else). SCCM has a TS configured and advertised to the Unknown Computers collection.

The DHCP server is configured for both DHCP and BOOTP requests (I added BOOTP as part of my troubleshooting, the default lease time is set to 5 minutes). It also has NAP enabled for the IPV4 addresses but disabled for this SCOPE. My host, the VM, the DHCP server, and the SCCM/WDS server are all on the same subnet. Juniper routers move the packets.

I'm testing PXE using a VirtualBox machine configured to network boot and it has an empty dynamically allocated disk attached. Wireshark is installed on both my host computer (running VirtualBox) and the DHCP server.

PROBLEM:

When the VM starts it performs a network PXE boot. I can see the discover request by the VM in Wireshark on both my host and the DHCP server. However, the DHCP server is not responding with an IP offer. If I could get some guidance as to where else to look for an error, or possibilities as to why it's not working, I'd appreciate it.

EDIT:

The dhcpsrvlog does not record an event regarding the request for an IP from the pxe client.

migrated from superuser.com May 2 '14 at 13:25

This question came from our site for computer enthusiasts and power users.

  • For your VM networking settings, are you using NAT or a Bridged Adapter? I had an issue similar to this while using NAT, switched it over to a bridged connection and it worked fine. I think it's in Settings > Network > Adapter 1 – Callen L May 2 '14 at 12:37
  • I started out with bridged, but did try NAT when bridged failed. The PXE client used a private address to try for DHCP so I knew that was a bad config and switched it back to bridge. I think the primary problem is that the DHCP server isn't responding to the request it's receiving, as evidenced by the wireshark capture. – Colyn1337 May 2 '14 at 12:41
  • Migrating due to user request. – Daniel Beck May 2 '14 at 13:25
  • If it's not bridged, how will it ever see the DHCP server? Fix that first. – Skyhawk May 2 '14 at 14:14
  • 1
    So, troubleshoot. You need to figure out where it's breaking down. Use Wireshark or tcpdump to look for DHCP broadcast traffic on the physical network. If it's there, why isn't it showing up in the server log? If it's missing, why isn't it hitting the physical network from the VM? You need to isolate the problem on one host or the other. That tells you which tree to bark up. Before you know it, the tasty squirrel will be yours. – Skyhawk May 3 '14 at 15:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.