A Windows Server 2008 terminal server stops listening on port 3389 when the server is under stress conditions

A Windows Server 2008 terminal server stops listening on port 3389 when the server is under stress conditions

Article ID : 954398
Last Review : July 3, 2008
Revision : 1.0


When you have more than 50 pending connections to a Windows Server 2008 terminal server, you notice the following symptoms:

• All the new logon requests fail.
• You receive the following error message on the client computer:

Server is not found in the network
• The PortQry utility or the Telnet utility report the status of port 3389 as Not Listening.

Note Clients that connect to a Windows Server 2008 terminal server use TCP port 3389 to communicate with the terminal server.

However, you do not notice any adverse symptoms on the terminal server. All existing sessions appear to work without interruption, as expected.

Back to the top


This behavior occurs in one of the following scenarios:

• The Windows Server 2008 terminal server assumes that it is under attack. In this scenario, the terminal server stops listening until the pending connection count goes down. You may find an event that indicates that the terminal server has stopped listening in the event log file.
• The pending connections cause the terminal server to consume more memory. The excess memory use may cause the TCP component to drop request packets.

Back to the top


To work around this behavior, change the value of the MaxOutstandingConnections registry entry to a number that is larger than 50. To do this, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control Terminal Server
3. In the details pane, double-click MaxOutstandingConnections.
4. Enter a value that is larger than 50, and then click OK.
5. Exit Registry Editor.

Back to the top


You can safely ignore this behavior as long as the terminal server continues to work as usual and as long as the terminal server does not restart when the load is reduced.

Back to the top


For more information about PortQry version 2.0, click the following article number to view the article in the Microsoft Knowledge Base:

832919 (/Feedback.aspx?kbNumber=832919/) New features and functionality in PortQry version 2.0

Back to the top

• Windows Server 2008 Standard
• Windows Server 2008 Enterprise
• Windows Server 2008 Datacenter

Back to the top

kbfix kbbug kbexpertiseadvanced kbtshoot KB954398

Back to the top


Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

AddThis Social Bookmark Button

Leave a Reply

To prove that you're not a bot, enter this code
Anti-Spam Image