Jeff, No, it was not recently, I had it already a few times last year but I will check the MaximumBlockSize entry
Mario From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Poling Sent: vrijdag 10 januari 2014 3:15 To: [email protected] Subject: Re: [mssms] PXE Issues Mario, Did you experience this issue recently? Thanks, Jeff On Fri, Jan 10, 2014 at 7:40 AM, Mario Van Uytsel <[email protected]<mailto:[email protected]>> wrote: Rebooting the DP did help me. Mario From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Jeff Poling Sent: donderdag 9 januari 2014 10:07 To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] PXE Issues I will certainly post if/when I get a resolution. Deleting a problem machine from ConfigMgr did not help my situation. In fact, the situation is more intermittent than I was led to beleive. It seems to impact two site DPs in particular; however, one of the sites has a machine that will PXE boot without issue. I did wireshark traces of both a failing machine and a successful machine at one site. The failed machine attempts to download one data block over and over again and finally fails. Should I resort to remvoing the PXE point and reinstalling? Thanks, Jeff On Thu, Jan 9, 2014 at 1:20 PM, Chris Thomas <[email protected]<mailto:[email protected]>> wrote: I'm on SCCM 2012 R2 and I've been running into E32 issues lately too. I haven't had Event ID 268 though. I've been having to restart the WDSServer service. Twice today and once yesterday. I have a handful of machines that need to be deleted from the console before PXE will answer them. I haven't tracked that down yet either. If you come up with a good answer could you try to reply back. -Chris On Thu, Jan 9, 2014 at 12:23 PM, Jeff Poling <[email protected]<mailto:[email protected]>> wrote: WDS is running. . . and this is occurring on multiple distribution points. . . Thanks, Jeff On Thu, Jan 9, 2014 at 11:09 AM, Brucker, Chris <[email protected]<mailto:[email protected]>> wrote: Can you verify that WDS is actually running? I have had issues before that permissions of the PXE Server have got messed up within AD which causes WDS to not start. I had to modify the SELF permissions on the PXE Server object within Active Directory to get WDS to start. Hope that helps. Thanks, Chris Brucker From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Jeff Poling Sent: Thursday, January 09, 2014 12:06 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] PXE Issues 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 ________________________________ The information contained in this message from First Financial Bancorp or its affiliates and any attachments are confidential. It is not intended for transmission to, or receipt by, anyone other than the addressee(s), or a person authorized to deliver it to the named addressee(s). If you have received this message in error, you are prohibited from copying, distributing or using the information. Please contact the sender immediately by return email and delete the original message.
