12/30/2009 5783 views
We have setup a Windows 2003 SP2 server with DHCP and WDS. WDS is configured in mixed mode as we plan to use legacy RIS images.

Problem is, PXE boot of physical workstation is not working. Following are the observations:
• Physical workstation network boot give “PXE E11 - ARP Timeout” error.
• DHCP and WDS are on same server and PXE option 60 is configured
• I can confirm DHCP is assigning IP to Physical workstation (from log file in System32\DHCP) but there is ‘No’ activity in WDSServer.LOG (Windows\Tracing).
• PXE boot of VMMachine hosted in same subnet works fine.
• PXE boot of same physical workstation from another RIS server also works fine.
• Network monitor shows, DHCP is sending MsgType = ACK with client IP address. After this message, client should send another request message asking for ServerHostName and BootfileName. There is no such message being received at server. Not sure if client is not sending this request or requesting is getting lost somewhere and is not reaching server.

I have been struggling to find clue of this issue but no success. Highly appreciate any help in this regard.
0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

Are all of your machines having issues or only machines on specific subnets? On subnets outside the DHCP/WDS server's local subnet, you'd have to configure PXE forwarding. Otherwise, the client response will be dropped at the router.
Answered 12/31/2009 by: airwolf
Red Belt

Hi Andy, yes, all machines were having issue and we had configured forwarding between subnets through IP helper.

Now, my issue is resolved.

In DHCP option3, we had configured two values for Router. One of these was not reachable. Removing unreachable default gateway, resolved the issue.

But why it was working on virtual platform, earlier as well, is still a mystery.
Answered 01/02/2010 by: kapil.kathuria
Orange Belt

  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.