Hello all,

I'm new to WDS, so please bear with me here...  We're trying to PXE boot our bare metal machines to a Linux DHCP server to connect them to our 2008 WDS server.  On a PXE boot we receive the PXE-T04 and PXE-E36 errors.  We have the server configured, and we are able to use TFTP to get the pxeboot.com file from a windows box using "TFTP -i [serverIP] get boot\x64\pxeboot.com.  However, when we try to get the same file from a linux box, it gives us an access violation error.  The only difference that I can see is that Linux uses the forward slashes, and Microsoft uses the back-slashes.  I found a post in another forum where someone said to change the ReadFilter registry value in "HKLM\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP" to read:

\boot\*
\tmp\*
/boot/*

I tried this and restarted the WDS server, but I still can't manually GET the pxeboot.com file from a Linux machine with either forward- or back-slashes.  The Linux build that we are using is CentOS 5.2, with DHCP 3.0.5-13.el5.

Hi There,

I have had sucess with this one as well, I run three servers, Win2003 DC + WEB + FTP, a Suse 10 Server, and a WIn2008 Imaging Server with WDS.

In the WDS console, right click your server - select properties. Select the DHCP tab and make sure the two options are unchecked, IIRC Do not listen on Port 67 and "set DHCP Option 60 to PXEClient". These options are need and will add the entries on your DHCP service ONLY if your DHCP runs on the same box as your WDS Service. However it does not apply at all if your DHCP server is a different machine and/or OS. Make sure you do not setup these options up on your seperate DHCP server manually. It works differently to old Linux & RIS PXE servers. WDS will automagically configure itself. Make sure your DNS works in both forward and reverse, even if you do your DNS on Linux.

Hope this helps you...