Popular Post sted Posted October 12, 2010 Popular Post Posted October 12, 2010 incase this happens to anyone else (just happened to me after installing an update on the server and a couple of clients i rebuilt wouldnt boot as they just hung waiting for a tftp offer) has happened to me after a windows update on server 2008 r2 (aparantly happens on straight 2008 as well) basically its due to having dns server on the same machine as wds dns pinches the ports the tftp service needs. This can leed to pcs not booting at all just sitting there failing to tftp if their boot order has lan set higher than hdd. 2008r2 fix run regedit go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WDSServer\Parameters Right-click UdpPortPolicy, and then click Modify. In the Value data box, type 0, and then click OK. On the File menu, click Exit to exit Registry Editor. Restart the Windows Deployment Services service. 2008 r1 Click Start Collapse this imageExpand this image, click Administrative Tools, and then click Windows Deployment Services. If there is no server that is listed under the Servers node, right-click the Servers node, and then click Add Server to add the local computer. In the navigation pane of the Windows Deployment Services MMC snap-in, expand the list of servers. Right-click the server for Windows Deployment Services, and then click Properties. Under Network, increase the UDP Port range. For example, if the current port range is 3,000 ports, increase the port range to 4,000 ports 34
loufarr Posted December 30, 2010 Posted December 30, 2010 Thanks. This worked on 2008 R2. Is this a bug that Microsoft addresses in their KB?
Achandler Posted January 5, 2011 Posted January 5, 2011 We've had this issue intermittantly and we use to reinstall and WDS server role and it would fix the problem (probably just updates the reg key really). We originally searched for a proper solution (though half the time Microsoft's solutions are reinstall it) but the issue happened so rarely and we've been so busy that it didnt seem worth it at the time.
kearton Posted February 1, 2011 Posted February 1, 2011 Thanks, Sted! That fixed my problem. It's always nice to Google a problem and end up back at good old Edugeek
sted Posted February 1, 2011 Author Posted February 1, 2011 Thanks, Sted! That fixed my problem. It's always nice to Google a problem and end up back at good old Edugeek thats why i put it here cos if nothing else im sure ill come across it again and at least i have a record of the fix lol
witch Posted February 1, 2011 Posted February 1, 2011 I don't need it yet but I am sure I will soon! Thanks!
ace971 Posted May 14, 2011 Posted May 14, 2011 Hi , I ran through this issue this morning. Didn't knew why that happened suddenly as everything was running smoothly and then I was annoyed as I didn't managed to get a single vm to boot on pxe. I have 2008 R1 running fine now by rising upd ports range. You saved my day
darshuhere Posted September 25, 2011 Posted September 25, 2011 Hey mate thank you very much this worked but dont know is this a bug of 2K8 R2 or what 1
servedchilled84 Posted October 12, 2011 Posted October 12, 2011 genius, absolute genius - that has saved me spending hours on a stupid error that I imagined taking up my day before throwing the computer out the window! mucho gracis
james-aus Posted December 5, 2011 Posted December 5, 2011 Hi Sted, Thank you for posting this fix, I am runnig SBS2008 with WDS & it worked for me also. It also happened after applying various Windows updates. Thought I was going to have to recover my WDS from a backup. I used the 2008 R1 fix. Thank you
Nulagrithom Posted January 23, 2012 Posted January 23, 2012 Thanks. I had WDS working on a clean install of 08 R2 just for test purposes. I shut it off for the night, booted it in the morning, and ran in to the TFTP timeout error. Tried a few other things before this fixed it!
mcdoodle Posted April 24, 2012 Posted April 24, 2012 Thanks Sted, I was trying to set up a pxe boot inside VM Workstation and could not get my client machine to connect to the server (2008 R2). This worked a treat - thanks for your help
peterfarrell Posted October 24, 2012 Posted October 24, 2012 Yeah, great fix pobably saved me spending half the day going through the Microsoft "help". Cheers mate!!
Jollity Posted January 14, 2013 Posted January 14, 2013 This problem still seems to be happening as I just encountered it. There does seem to be a Microsoft Knowledge Base article on it now at least.
sted Posted January 14, 2013 Author Posted January 14, 2013 I suspect its due to running wds on a dc but when you have 1 server tough
superhl Posted March 20, 2013 Posted March 20, 2013 Arrived to work this morning and same problem. thanks for the fix
garethm Posted April 3, 2013 Posted April 3, 2013 Just came and found this issue when I have 5 brand new ThinkCentre Edge PCs to build... THANK YOU!!!
tungst3n Posted May 7, 2013 Posted May 7, 2013 This thread may be nearly three years old but this just fixed a WDS on one of my sites. Thanks for the fix.
Griff Posted June 21, 2013 Posted June 21, 2013 Good fix thanks, did not solve my problem immediately but if anyone else is still having the same problem after this fix check that your UDP Port Range in the Network Settings of WDS are set from 50000 to 65000 seems to have fixed the issue for me. 1
Menov321 Posted September 12, 2013 Posted September 12, 2013 This saved my clonezill asetup thanks so much incase this happens to anyone else (just happened to me after installing an update on the server and a couple of clients i rebuilt wouldnt boot as they just hung waiting for a tftp offer) has happened to me after a windows update on server 2008 r2 (aparantly happens on straight 2008 as well) basically its due to having dns server on the same machine as wds dns pinches the ports the tftp service needs. This can leed to pcs not booting at all just sitting there failing to tftp if their boot order has lan set higher than hdd. 2008r2 fix run regedit go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WDSServer\Parameters Right-click UdpPortPolicy, and then click Modify. In the Value data box, type 0, and then click OK. On the File menu, click Exit to exit Registry Editor. Restart the Windows Deployment Services service. 2008 r1 Click Start Collapse this imageExpand this image, click Administrative Tools, and then click Windows Deployment Services. If there is no server that is listed under the Servers node, right-click the Servers node, and then click Add Server to add the local computer. In the navigation pane of the Windows Deployment Services MMC snap-in, expand the list of servers. Right-click the server for Windows Deployment Services, and then click Properties. Under Network, increase the UDP Port range. For example, if the current port range is 3,000 ports, increase the port range to 4,000 ports
andyire Posted October 22, 2013 Posted October 22, 2013 In case anyone else gets this error and they have tried both increasing the port range and tweaking the UDPportPolicy setting via the registry, I have found another possible cause and solution. In the past I have found that either "increasing the port range" or "tweaking the UDPportPolicy via the registry" sorts any problems that I have had with WDS and client computers displaying the PXE - tftp open timeout errors when attempting to download images. Naturally these were the first things I tried when I came to work today and found that other techs were reporting clients displaying the infamous open timeout error. Unlucky for me this didn't work. Solution 1)Looking in the "Application and Services Log> Deployment-Services-Diagnostics" -on the WDS Server, I could see that the client was booting and talking to the WDS server successfully. IP on the clients PXE boot screen tallied with the IP logged on the WDS server with this event below; Event ID: 4096 The Following Client PXE Booted: MAC: 00000000000000BLAHBLAH IP: 123.123.123.50 I could see however that the server wasn't logging any of the following normal events to signify that the client managed to get the boot wim. Event ID's: 4099 or 4100 The Following Client started the TFTP Download 2) Looking in "Windows Logs> Application" I discovered this lovely error message, indicating trouble with UDP port 69 when setting up the TFTP endpoint. Event ID: 772 An error occurred while trying to create the UDP endpoint for WDSTFTP provider on interface 123.123.456.26:69. This can happen if the network interface was disabled or changed, or some other application is already using the port. The provider will not be able to receive requests on this interface. Error Information: 0x2740 3)Next, I dumped the info about ports running using; netstat -abn >> NewFile.txt Searching the output for port 69 I discovered that javaw.exe was the culprit. UDP 123.123.456.26:69 *:* [javaw.exe] As it turns out there had been an update for java a few days before this, after a restart javaw.exe decided it wanted to use port 69, which WDS requires for TFTP. Javaw.exe managed to nab the port before WDS got a chance, thus our lovely open timeout error. 4) I killed the javaw.exe process 5) Restarted the WDS service & boom, back in action, no more TFTP open timeout errors. OK, I hope this helps someone else. 1
free780 Posted November 30, 2013 Posted November 30, 2013 How come your running wds on the same server as dns?
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