CHR1S Posted July 3, 2012 Posted July 3, 2012 DHCP Options 060 - PXEClient 066 - Points to the IP of the WDS server 067 - Boot\Customx64\wdsnbp.com TFTPD Directory - H:\OSDeploy The above 067 lives in this directory and is present The PC attempts to boot the download the file but gives the PXE-T01 & E3B errors Dont know where the TFTPD log file lives for the built in SERVER 2003 R2 tftpd.exe Anyone got any pointers please?
Gatt Posted July 3, 2012 Posted July 3, 2012 It will be your 067 option - are you sure that path is correct for WDS? I know SCCM requires it to be set, but not sure if WDS needs it too?
PotNoodleTech Posted July 4, 2012 Posted July 4, 2012 AFAIK you only need 066 set so that PXE client can see the PXE server. The WDS server decides what image to use and passes that on to the client, you don't need to specify it. Try getting rid of 060 and 067 and see if that works.
Gatt Posted July 4, 2012 Posted July 4, 2012 Also, where is your DHCP server? If it's on the same PC as your WDS server, then you will need to enable the options on the DHCP Tab under the WDS Server Properties. If its not. then as @AButters says, you should only need to enable option 066... Also, have you added the boot image to WDS - I have a feeling that WDS might not like your customx64 folder and may insist you use its own boot\x64\ folder
CHR1S Posted July 4, 2012 Author Posted July 4, 2012 Thanks for the pointers guys, I will give them a try when im back in the school tomorrow.
CHR1S Posted July 6, 2012 Author Posted July 6, 2012 No luck, I swapped the boot locations back to the default, removed the 066 and 067 entries checked the DHCP settings (both on same server) and still get the TFTP error. What I have found is that there is no entry for WDSTFTP in the registry (where it sets its boot path) HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\ Name: RootFolder Type: REG_SZ Data: Can you just re-install the WDSTFTPD component?
CHR1S Posted July 6, 2012 Author Posted July 6, 2012 Seems that under 2003R2 its in a different location HKLM\System\CurrentControlSet\Services\TFTPD\Parameters Entry - DIRECTORY Whatever I set in there I still get the errors, if I delete the key WDS service fails to start.
CHR1S Posted July 6, 2012 Author Posted July 6, 2012 Removed and Reinstalled WDS to its default locations. Seems to have sort of fixed it, just doing some more testing to see if it allows me to load the PE image
CHR1S Posted July 10, 2012 Author Posted July 10, 2012 Getting the process just stop at TFTP Download: Boot\x64\bootmgfw.efi Just sits there forever with no errors
CHR1S Posted July 10, 2012 Author Posted July 10, 2012 Urgh, I didnt add an x86 boot image, as Im imaging x64, but it seems to want to boot from x86 only! d'oh!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now