If you try to set up TCP connections from ports that are greater than 5000, the local
computer responds with the following WSAENOBUFS (10055) error message:
An operation on a socket could not be performed because the system
lacked sufficient buffer space or because a queue was full.
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
How to back up and restore the registry in Windows
The default maximum number of ephemeral TCP ports is 5000 in the products that are included in the "Applies to" section. A new parameter has been added in these products. To increase the maximum number of ephemeral ports, follow these steps:
- Start Registry Editor.
- Locate the following subkey in the registry, and then click Parameters:
- On the Edit menu, click New, and then add the following registry
Value Name: MaxUserPort
Value Type: DWORD
Value data: 65534
Valid Range: 5000-65534 (decimal)
Default: 0x1388 (5000 decimal)
Description: This parameter controls the maximum port number that is used when
a program requests any available user port from the system.
Typically, ephemeral (short-lived) ports are allocated between
the values of 1024 and 5000 inclusive. After the release of security bulletin MS08-037, the behavior of Windows Server 2003 was changed to more closely match that of Windows Server 2008 and Windows Vista.
For more information about Microsoft security bulletin MS08-037, click the following article numbers to view the articles in the Microsoft Knowledge Base:
MS08-037: Description of the security update for DNS in Windows Server 2008, in Windows Server 2003, and in Windows 2000 Server (DNS server-side): July 8, 2008
MS08-037: Description of the security update for DNS in Windows Server 2003, in Windows XP, and in Windows 2000 Server (client side): July 8, 2008
MS08-037: Vulnerabilities in DNS could allow spoofing
- Exit Registry Editor, and then restart the computer.
An additional TCPTimedWaitDelay registry parameter determines
how long a closed port waits until the closed port can be reused.
For more information about a related topic, visit the following Microsoft Web site:
For more information about a related topic, click the following article numbers to view the articles in the Microsoft Knowledge Base:
TCP/IP and NBT configuration parameters for Windows 2000 or Windows NT
TCP/IP and NBT configuration parameters for Windows XP
Technical support for x64-based versions of Microsoft Windows
If your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you must have technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Windows Server 2003 x64 edition separately, contact Microsoft for technical support.
For product information about Windows XP Professional x64 Edition, visit the following Microsoft Web site:
For product information about x64-based versions of Windows Server 2003, visit the following Microsoft Web site: