From time to time, your system may report Destination Service Event ID 1036. There can be several reasons for this error to occur.
|Description||Could not create terminal server class. The corresponding status was 0xc0000022|
|Event Information||When trying to use a user computer running Microsoft Windows XP to log on to a remote desktop. An XP computer hosting the exact remote connection desktop may not connect successfully, and the client computer may receive the following error messages:
The client was unable to connect to the computer of the remote device.
The most common causes of errors:
|Reference Links||You may get the latest version of “The client could not connect to the remote computer” when you try to create a connection to virtual remote desktop with a computer running Windows XP|
We work with you to quickly identify cyberthreats
and prevent events before they cause damage.
Case 1. ThisThe problem may indicate that a second application is running on the terminal server.on the same TCP port as RDP (Remote Desktop Protocol). relapseThe port assigned for RDP is considered to be 3389. You can compare with Pulist which softwareUse connector 3389. Maybe this guide will help you.
Case 2. WhenWhen you use RDC to make a final terminal service connection, you may receive an event ID of 1036 andone in the following message:
Clientindeed can connect to the remote computer.
The remote link may not be enabled.The price or the computer itself may be too busy for you.accept new connections.
In this way, potential network problems protect your connection.
Please try logging in later. If the problem persists,contact the administrator.
Reason:The network card is not bound to the RDP-TCP connection. To solve the problem, make sure I say thisthat the correct network adapter is bound so that it establishes an RDP-TCP connection. Do it,Track steps:
1. On the server, connect locally to the server (do not generateDesktop/terminal client).
2. Click “Start”, “Run”, type “tscc.msc /s” (without quotes) and clickGood.
3. In the terminal, double-click the Basic Services Configuration snap-in on connections,then RDP-TCP on the right panel.
4. In the “Network” tab, click “Adapter”, select our correct network adapter andClick OK.
5. Make sure you can connect to the server using RDP.
Case 3:No one can access TS with event ID 1036: TerminalFailed to create server session. Corresponding status code, probablySure, it was 0x2740. vError code 0x2740 = decimal 10048. which means exactly “One time use with eachThe socket address (protocol/network address/port) is simply allowed.When configuring Terminal Services, RDP was configured directly so that only the session was listening.only one
Case 4: OneIn another case with code 0x2740, the client was running Windows Server 2003.Service Pack 1 via RDC. After installing Terminal ServicesConfiguration setting, RDP only listened to everything inside(trusted) interface.
Case 5. See whatUser “The receiving client may be far from connecting to the unlikely”Computer” error message with Event ID 1036 when you try to createRemote desktop connection to the best computer based on Windows XP. To solve someProblem, get a solution from Microsoft. For more information click on yournext article number to view study in Microsoft KnowledgeBase:Get this software today and fix your PC problems for good.