Article ID: 329155 - Last Review: January 4, 2005 - Revision: 4.0 You receive a "The server may be too busy" error message when you try to connect to Terminal Services on a Small Business Server 2000 computer
This article was previously published under Q329155 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
SYMPTOMS
When you try to connect to Terminal Services on a Microsoft Small Business Server (SBS) 2000 computer, you may receive the following error message:
The client could not connect to Terminal Server.
The server may be too busy.
Please try connecting later. CAUSEThis error may occur if another process that is running on the SBS 2000 computer starts using TCP port 3389 before the Terminal Services service starts. By default, TCP port 3389 is the port that Terminal Services uses for its connections. If another process is using this port, terminal server connections may fail. The process that most frequently causes this problem is the Microsoft Exchange System Attendant service (Mad.exe). That is because Microsoft Exchange uses remote procedure call (RPC) dynamic port allocation. During RPC dynamic port allocation, the RPC service assigns an RPC program a random port number that is more than 1024. Occasionally, RPC may assign TCP port 3389 to a program such as the Microsoft Exchange System Attendant service. WORKAROUNDWARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own
risk. To work around this problem, modify the registry to exclude TCP port 3389 from the RPC port range. To do this, follow these steps:
For additional information about how to configure RPC port ranges, click the following article number to view the article in the Microsoft Knowledge Base: 154596
(http://support.microsoft.com/kb/154596/
)
How to configure RPC dynamic port allocation to work with firewalls
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|





















Back to the top