You receive an error message when you run a custom Winsock network program on a Microsoft Windows XP Service Pack 2-based computer (905628)
The information in this article applies to:
- Microsoft Windows XP Professional Service Pack 2 (SP2)
SYMPTOMSWhen you run a custom Winsock network program on a Microsoft Windows XP Service Pack 2 (SP2)-based computer, you receive the following error message: Error 10055 = WSAENOBUFS An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. Note The error message that you receive may be different depending on the program that you are using. This symptom occurs if the Windows XP SP2-based computer does not have network connectivity. RESOLUTIONA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows XP service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name
--------------------------------------------------------
15-Aug-2005 23:58 5.1.2600.2739 360,576 Tcpip.sys
15-Aug-2005 23:46 5.1.2600.2739 30,720 Arpidfix.exe To work around this problem, install the Microsoft Loopback Adapter. To install the Microsoft Loopback Adapter, follow these steps: - Click Start, and then click Control Panel.
- If you are in Classic view, click Switch to Category View.
- Click Printers and Other Hardware.
- Click Add Hardware, and then click Next.
- Click Yes, I have already connected the hardware, and then click Next.
- Click Add a new hardware device, and then click Next.
- Click Install the hardware that I manually select from a list, and then click Next.
- Click Network adapters, and then click Next.
- In the Manufacturer box, click Microsoft.
- In the Network Adapter box, click Microsoft Loopback Adapter, and then click Next two times.
- Click Finish.
Note After you install the Microsoft Loopback Adapter, you can manually configure its options. If the TCP/IP properties are configured to use the Dynamic Host Configuration Protocol (DHCP), the Microsoft Loopback Adapter eventually uses an autonet address (169.254. x. x/16). The Microsoft Loopback Adapter eventually uses an autonet address because the adapter is not actually connected to physical media.
By default, TCP/IP properties are configured to use DHCP.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 7/24/2006 |
---|
Keywords: | kbQFE kbHotfixServer kbWinXPsp2fix kbfix kbbug kbpubtypekc KB905628 kbAudITPRO |
---|
|