After more investigation, I found that the problem started at one site on
Jan 8.  I also found that HP driver updates were isntalled on the DPs on
Jan 6.  While I don't have a definitive smoking gun, my hunch is that the
HP NIC driver update is the root cause.

The fix I found is documented in http://support.microsoft.com/kb/975710.

I added the MaximumBlockSize entry and set it to 1024.  As soon as I did
that, PXE boots started working without issue.

I probably should have tried the MaximumBlockSize sooner, but I just could
not believe it was needed :)

For what it's worth.

Jeff


On Thu, Jan 9, 2014 at 11:06 AM, Jeff Poling <[email protected]> wrote:

> I am grasping at straws here. . .I have 7 sites with ConfigMgr 2012 SP1
> CU2 distribution points.  The OS on the servers is Windows Server 2008 R2.
> PXE is failing with a TFTP timeout.  THe error code is PXE-E32 TFTP Open
> timeout.
>
> I just was informed abut this issue, and I guess it has been occurring for
> the last couple of weeks.  The only change I can so far determine is that
> December Windows Updates were installed just before Christmas.
>
> In addition, I do see an event log error entry for WDSIMGSRV that is event
> ID 268.  It does not have a lot of detail, but it occurs on each server
> that has PXE issues.
>
> Are there any known issues with updates from December impacting PXE?
>
> Thanks,
>
> Jeff
>
>


Reply via email to