iPXE discussion forum

Full Version: Can't PXE Boot WDS/SCCM from iPXE?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
For this example, I am loading iPXE from an ISO in a VM. No scripts or anything, just trying to PXE Boot. The results have been the same if I chainload on real hardware or boot iPXE from USB.

WDS 2012 is setup in proxyDHCP mode. I can boot to it fine from normal PXE and old versions of gPXE from 2010. This also worked with iPXE in the past, although I have not needed it recently so I do not know when it broke. The WDS server has remained unchanged except for windows updates.

The the current version of iPXE (from this link: http://boot.ipxe.org/ipxe.iso) gives me this:
[Image: R0wlKUP.png]

[Image: Q6Ypj0B.png]

[Image: CgiVwab.png]

The first thing I noticed is that WDS thinks it was launched in DHCP Referral mode. This is NOT the case. The DHCP server on this subnet does not provide a filename or next-server. WDS is on a different server then DHCP and runs in proxyDHCP mode. The config page in iPXE makes it appear that everything is setup correctly. Booting from this server in the same VM without iPXE does not show a DHCP Referral.

Any ideas? Thank you.
After reading through the mailing list archives, I was able to find that this is a known issue with the current version: http://lists.ipxe.org/pipermail/ipxe-dev...03933.html
Yeah, the leading "/" character is known to cause some issues with Windows TFTP servers, but there is a workaround available, you just need to change what the TFTP server accepts in terms of path separators or root locations. You might find some answers by enabling WDS debugging, as explained at http://support2.microsoft.com/kb/936625 and http://2pintsoftware.com/enabling-wds-debug-logging/.
Wow, thanks. This page had all the answers I was looking for: http://ipxe.org/appnote/chainload_wds

Is there an easy way to list all the articles on the Wiki? I have found some very informational pages through searches that do not seem to be visible on the http://ipxe.org/docs page or anywhere else on the site.
Reference URL's