OSD, WDS and PXE issue - PXE Service Point not responding - error 10048
Hi all, Have the common PXE-E53 "No boot filename received" issue, but can't get to the bottom of it this time. DHCP Server and PXE Service Point on different servers, in same subnet. Client in different subnet, IP Helper configured forwarding to both. (Have tried using DHCP Options 60,66,67 with no difference). On SCCM PXE Service Point, WDS running without error. PXE Service Point running, but the following error "PXE Control Manager detected PXE service point is not responding to PXE requests. The error is 10048." PXEControl.log has the following which seems to indicate a bind issue? ) SMS_PXE_SERVICE_POINT successfully STARTED. ******************************************************************************** Configuration and Availability Monitor thread started. Initialized 'SMS Server Availability' performance instance => SMS PXE Service Point. adding address to server list 10.01.101.146 adding address to server list 127.00.00.01 Bind Socket Failed Error initializing PXE client Bind Socket Failed Error initializing PXE client Pxe test request failed, error code is 10048. STATMSG: ID=6319 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PXE_SERVICE_POINT" SYS=xxx36 SITE=SV0 PID=4600 TID=1676 GMTDATE=Fri Nov 12 16:26:29.760 2010 ISTR0="10048" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_PXE_SERVICE_POINT PXE test request failed, status code is -2147014848, 'Error initializing PXE client'. Successfully performed availability check against local computer. Initialization still in progress. Thanks in advance for any ideas of what to check next.
November 12th, 2010 4:33pm
is the dhcp server non-microsoft ? and have you checked the portfast settings on your cisco switch assuming you have such a switch ? My step by step SCCM Guides I'm on Twitter > ncbrady
November 12th, 2010 7:04pm
Thanks for the response Niall, Windows 2003 DHCP Server. DHCP forwarding works fine, just PXE problem. Have to check with netowrk guys about portfast - large cisco network - no other issues. Regular DHCP clients fine for years. Can you give me more specific guidance for network guys to check and maybe point me to some background? Thanks.
November 13th, 2010 4:40am
Verify that you actually have netboot files in both x86 and x64 locations. They are being extracted from the boot images that you add in ConfigMgr 2007. Check the \Remoteinstall\Smsboot\x86 and \Remoteinstall\Smsboot\x64 folders, there should be 5 files in the x86 folder, and 6 files in the x64 folder. There is also a WDS cacheexpire value that can cause problems, I recommend setting it to 120 rather than the default 3600 (seconds). / Johan
November 14th, 2010 6:55am
Error 10048 signifies "Only one usage of each socket address (protocol/network address/port) is normally permitted." It indicates that the PXE Service Point is unable to bind itself on port 4011, which is used by PXE Service Point. Do one of the following: Enter the following command in the command prompt on a Windows XP or Windows Server 2003 computer to display the active connections being used by the TCP/IP protocol on this computer: netstat -n This will list the TCP/IP addresses bound to the client computer and the ports on which the TCP/IP addresses are communicating with a remote server. If the listed ports consume all of the available ports then TCP/IP port exhaustion occurs. Enter the following command in the command prompt on a Windows Server 2003-based client computer to display the active connections being used by the TCP/IP protocol: netstat -b This will list the TCP/IP address bound to the client computer, the port on which the TCP/IP address are communicating with a remote server, and the application that is using the ports. This information can help determine which client applications are consuming excessive TCP/IP ports. Disable all 3rd party applications running on the WDS/PXE Service Point Server and try again. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
November 16th, 2010 3:42am
Thank you Eric. Yes that was the prblem. I moved the WDS/PXE Service Point on to a seperate dedicated machine and the issue was resolved. (Naturally I also had to change IP Helper address on the router interface to reflect the new IP address of the PXE Service point.) The explanation of error 10048 was exactly what I needed to understand the isse - thanks again.
November 17th, 2010 10:15am