Error 10048 Unable To Bind Socket To Port 4011
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: OSD, WDS and PXE issue - PXE Service Point not responding - error 10048 System Center Configuration Manager > Configuration Manager 2007 General Question 0 Sign in to vote Hi all, Have http://www.symantec.com/connect/forums/error-msg-when-trying-start-pxe-and-bootp-server 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 https://social.technet.microsoft.com/Forums/en-US/1a0972f1-ede9-4dfe-b3c3-dc98245f7c15/osd-wds-and-pxe-issue-pxe-service-point-not-responding-error-10048?forum=configmgrgeneral 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:
issues, feature requests, help, etc. Moderators: Curtis8, A_Null Post Reply Print view Search Advanced search 9 posts • Page 1 of 1 anexeon11 Posts: 2 Joined: Fri May 09, 2008 10:28 pm Tftpd32 cannot bind the Tftpd port Quote Postby anexeon11 » Fri May 09, http://ping.windowsdream.com/forum/viewtopic.php?t=6780 2008 10:36 pm When trying to execute the tftpd32 program on Server 2003 Enterprise sp2; I http://www.verycomputer.com/1_17902f08e1e7bca8_1.htm get an "Error 10048 Only one usage of each socket address is permitted. Tftpd32 can not bind the TFTP port. an application is already listening on this port" I tried changing the port in settings and no luck. please advise. Top anexeon11 Posts: 2 Joined: Fri May 09, 2008 10:28 pm Never mind! Quote Postby anexeon11 » Mon May 12, 2008 4:49 pm I found the error 10048 other software which was binding that port. Top Curtis8 Site Janitor Posts: 985 Joined: Thu Mar 01, 2007 3:22 pm Location: Canada Contact: Contact Curtis8 ICQ Website WLM Yahoo Messenger AOL Quote Postby Curtis8 » Tue May 13, 2008 4:46 am Which program was it? Just in case someone else has the same issue. CurtisIf you can read this, help me by going to the following link (can only go once per day)http://s13.bitefight.org/c.php?uid=32058Thank you Top fossphur Posts: 15 Joined: Wed Dec 05, error 10048 unable 2007 8:24 am Same problem here Quote Postby fossphur » Wed May 14, 2008 9:12 am Only... I can't find what program is getting the port. I have tftpd32 set to run as a service so I would have thought it would "get in first" and the other program would miss out on the port. Anyway it doesn't seem to matter what processes I terminate, I'm still getting the same "no boot filename received" error. Top fossphur Posts: 15 Joined: Wed Dec 05, 2007 8:24 am Quote Postby fossphur » Wed May 14, 2008 9:18 am Odd, I downloaded active port to see what was going on. And there is nothing else using port 69. I can't see any other BootP daemons running (or whatever it is that the error message claims). The pxelinux.0 file is where it should be, and so on, and still nothing will PXE boot. Top fossphur Posts: 15 Joined: Wed Dec 05, 2007 8:24 am Quote Postby fossphur » Wed May 14, 2008 9:34 am Ok I found on another website that tftpd32 likes to have access to ports 67,68,69 and 4011. Sure enough, ports 67 and 68 had tcpsvcs.exe running on them. I terminated the process not caring what it was, only to see it start itself up again. Duh, its a service, what was I expecting? Anyway I terminated the service and quickly got tftpd32 restarted and it got in fast enough to claim the ports it w
server which is running DHCP. The PXEClient Option 60 tag had been added to the DHCP server. This had been working just fine for multicasting images until the other day...clients suddenly were no longer able to boot to the network, and it was discovered that the 3Com PXE service was not working. Attempts to start the service result in it stopping almost immediately. When one goes to the Win2k start menu and clicks on 3Com PXE, the following error message will pop up: Error 10048: unable to bind socket to port 4011 Uninstalling and reinstalling the programs does nothing to solve this problem. There is an article in the Symantec KB referencing this particular error number, but it does not apply here. Posting to the Symantec message board got me a referral to the 3Com website. Maybe I wasn't looking in the right place, but I only found general articles in reference to the 3com boot services there. If anyone could give me any advice on this, I'd really appreciate it, thanks. Top 1. Symantec Ghost or .... Hi, We are ghosting our server quite often. But to use ghost we have to turn of the server. Is there any option to make ghost without shuting down? Maybe there are another programs which can make copy of the whole disk (partition) without shuting system down. Bafi generic levitra india2. NTDS Replication Error 1084 3. Symantec Ghost 4. Increase Traffic...Post Free Links 5. Symantec Ghost Question 6. Auto-create printers never going away... 7. Symantec Ghost 8. Finally able to connect via Dial-Up Networking, but... 9. Symantec Ghost 7.0 peer-to-peer problem 10. Symantec's Ghost 2001 not all it is cracked up to be (long) 11. Ghost 6.5 (Symantec) 12. Question about Symantec Ghost 13. W2K install with Symantec Ghost 1 post • Page:1 of 1 All times are UTC Board index Spam Report