Home | Site Map | Cisco How To |  Net How To | Wireless | Search | Forums | Services | Donations | Careers | About Us | Contact Us|

Event ID 1036 - Terminal Server session creation failed

Case 1: This problem could indicate that another application on the terminal server is using the same TCP port as the Remote Desktop Protocol (RDP). The default port assigned to RDP is 3389. You may use PULIST to check which software is using the port 3389. this how to may help.

How to find open ports on a computer

Case 2: When using RDC connect to a terminal service, you may receive Event ID 1036 and one of the following message:

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.

Cause: the NIC is not bound to RDP-TCP connection. To resolve the problem make sure that the correct network adapter is bound to RDP-TCP connection. To do this, follow these steps:
1. On the server, logon to the server locally (not using Remote Desktop/Terminal Client).
2. Click Start, Run, type "tscc.msc /s" (without qutation marks and click OK.
3. In the Terminal Services Configuration snap-in double-click Connections, then RDP-Tcp in the right pane.
4. Click the Network Adapter tab, select the correct network adapter and click OK.
5. Make sure that you can establish an RDP connection to the server.

Case 3: You can’t access TS with Event ID 1036:  Terminal Server session creation failed. The relevant status code was 0x2740. The error code 0x2740= decimal 10048., which means "Only one usage of each socket address (protocol/network address/port) is normally permitted." The Terminal Services configuration was setup the RDP protocol to only listen to one session only

Case 4: in other case of the code 0x2740, one client installed Windows Server 2003 Service Pack 1 over RDC. After the installation, the Terminal Services configuration was setup the RDP protocol to only listen on the inside (trusted) interface.

Case 5: the user receive "The client could not establish a connection to the remote computer" error message with Event ID 1036 when he tries to establish a remote desktop connection to a Windows XP-based computer. To resolve this problem, obtain the hotfix from Microsoft.. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 (http://support.microsoft.com/kb/322389/) How to obtain the latest Windows XP service pack.

 Post your questions, comments, feedbacks and suggestions

Contact a consultant

Related Topics