Hello! I am having some PXE boot errors and WDS errors. First off I was getting an TFTP error. I fixed this error by redoing PXE and WDS, but it keeps coming back after several machines get imaged. PXE-E32 TFTP open timeout After restarting WDS it seems to work for a couple of machines then it crashed and does the same thing. Here are some of the errors in get in the log file. [010.050.000.222:67] Recv From:[010.002.018.251:67] Len:548 16c9070 smspxe 6/26/2012 4:17:30 PM 5832 (0x16C8) [010.050.000.222:67] Recv From:[010.002.018.250:67] Len:548 4ee970 smspxe 6/26/2012 4:17:30 PM 3064 (0x0BF8) [010.050.000.222:67] Recv From:[010.002.018.251:67] Len:548 1478430 smspxe 6/26/2012 4:17:32 PM 3064 (0x0BF8) Ignoring req from [010.002.018.251:67] Dest Server:[010.050.000.160] smspxe 6/26/2012 4:17:32 PM 3064 (0x0BF8) [010.050.000.222:67] Recv From:[010.002.018.250:67] Len:548 1775e30 smspxe 6/26/2012 4:17:32 PM 5832 (0x16C8) Ignoring req from [010.002.018.250:67] Dest Server:[010.050.000.160] smspxe 6/26/2012 4:17:32 PM 5832 (0x16C8) [010.050.000.222:4011] Recv From:[010.002.018.182:68] Len:548 12cf630 smspxe 6/26/2012 4:17:32 PM 5832 (0x16C8) [010.050.000.222:4011] Recv From:[010.002.018.182:68] Len:303 16c8bb0 smspxe 6/26/2012 4:17:32 PM 5832 (0x16C8) Executing GetBootAction(29933, EISD-SCCM) smspxe 6/26/2012 4:17:32 PM 5240 (0x1478) No Boot Action for Device (29933) found smspxe 6/26/2012 4:17:32 PM 5240 (0x1478) ProcessDatabaseReply: No Advertisement found in Db for device smspxe 6/26/2012 4:17:32 PM 5240 (0x1478) I added the machine with a computer association by MAC address. When i go back into the collection I do not see the machine association. This is really throwing me for a loop. Thanks, Mark-

I had a similar issue and applied this hotfix and it resolved the problem. http://support.microsoft.com/kb/980270

This is for SP2. I am on R3. Will it still work on R3?Thanks, Mark-

Just have a look at this guide for more information: http://www.bootix.com/support/problems_solutions/pxe_e32_tftp_open_timeout.html It mentions: Make sure that a TFTP server is set up and running. When the TFTP service is running on a different machine than the DHCP or BOOTP service, you need to add option 066 (next-server) to the DHCP/BOOTP server configuration, and set this option's value to the IP address or "resolvable hostname" of the TFTP server. When option 066 (next-server) is not defined, the PXE client assumes that the TFTP service is running on the same machine from which it received its DHCP/BOOTP configuration information.My blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn

ok now I am having a different issue related to this. The TFTP error has gone away now. I am now getting a TFTP Download: smsmboot\x64\abortpxe.com Looked at logs and this is what i found for a couple of machines. The SMS PXE Service Point intructed device to boot normally since it has no PXE advertisement assigned. Device Mac address (mac address). Which is strange as I have done a computer association for this machine. Looks as if the association did not take so I did it again with no result. ???????????????????/Thanks, Mark-

Did you apply the hotfix. Yes, this will apply to R3.

Yes i applied the hotfix and also changed hte CacheExpire registry settings and it fixed my issues.Thanks, Mark-