You can't establish a Remote Desktop session to a computer running one of the affected products
This article provides a solution to an error that occurs when you try to connect to the Terminal service running on one of the affected products.
Applies to: Windows Server 2003
Original KB number: 555382
When you try to connect to the Terminal service running on one of the affected products, you receive the following error message:
Remote Desktop Disconnected
The client could not connect to the remote computer.
Remote connections might not be enabled or the computer might be too busy to accept new connections.
It is also possible that network problems are preventing your connection.
Please try connecting again later. If the problem continues to occur, contact your administrator.
Additionally, when you view System Event log on the affected server you see the following event:
Event Type: Error Event Source: TermService Event Category: None Event ID: 1036 Date: <DateTime> Time: <DateTime> User: N/A Computer: Servername Description: Terminal Server session creation failed. The relevant status code was 0x2740. For more information, see Help and Support Center at.
To resolve the problem, make sure that the correct network adapter is bound to RDP-TCP connection. To do it, follow these steps:
- On the server, sign in to the server locally (not using Remote Desktop/Terminal Client).
- Select Start, Run, type tscc.msc /s (without quotation marks and select OK).
- In the Terminal Services Configuration snap-in, double-click Connections, then RDP-Tcp in the right pane.
- Select the Network Adapter tab, select the correct network adapter, and select OK.
- Make sure that you can establish an RDP connection to the server.
Alternative resolution steps. Use these steps only if you can't do local sign-in to the affected server.
Using Registry Editor incorrectly may cause serious problems that may require you to reinstall your operating system. Use Registry Editor at your own risk and only after making backup of full Registry and the keys you are going to change.
Start Registry Editor (Regedt32.exe).
Select File\Connect network Registry. Enter computer name or IP address and select OK. Firewalls between your computer and the affected server may prevent successful connection. Remote Registry service should be running on the server.
Navigate to the following registry key (path may wrap):
Under this key are one or more keys for the globally unique identifiers (GUIDs) corresponding to the installed LAN connections. Each of these GUID keys has a Connection subkey. Open each of theGUID\Connection keys and look for the Name value. Choose the connection you want Terminal Services to use.
When you have found the GUID\Connection key that contains the Name setting that matches the name of your LAN connection, write down or otherwise note the GUID value.
Then navigate to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\lanatable. Using the GUID you noted in step 5 select subkey. It's LanaId.
Navigate to the following value:
Change it's data to the value you noted in step 6. If you want RDP to listen on all LAN adapters enter value of 0.
Community Solutions Content Disclaimer
Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.