Export (0) Print
Expand All

3.1 Example 1: Connecting from an RDP Client to an RD Session Host

This example demonstrates the process of connecting from an RDP client to an RD Session Host as described in section 2.5.1.1.

Prerequisites

  • A valid, non-expired license exists for the client on the License Server.

  • The RD Session Host server is operational and listening for an RDP connect request on port 3389. If the RDP client is using the IPv6 protocol, the RD Session Host supports the IPv6 protocol.

Initial System State

The RDP client and RD Session Host are not connected.

Final System State

The RDP client is connected to the RD Session Host; the RDP client can start sending mouse and keyboard input to the RD Session Host; and the RD Session Host can send graphics output to the RDP client.

Sequence of Events

The diagram that follows illustrates one example of the messages that are exchanged between an RDP client and an RD Session Host in an environment where no intermediary gateway is used. The sequence of Connection Finalization events (steps 15-23) is not fixed, and the possible message flow is specified in detail in [MS-RDPBCGR] section 1.3.1.1.

MS-RDSOD

Figure 6: Sequence illustrating RDP Client connecting to an RD Session Host

The connection sequence is described in the following steps.

  1. The RDP client initiates the connection when the user provides the name of the remote desktop to connect to. The RDP client initiates a connection to the RD Session Host by sending an X.224 Connection Request protocol data unit (PDU), as described in [MS-RDPBCGR] section 1.3.1.1.

  2. The RD Session Host responds with an X.224 Connection Confirm PDU.

  3. The RDP client sends a Multipoint Communication Service (MCS) Connect Initial PDU with GCC Conference Create Request.

  4. The RD Session Host responds with an MCS Connect Response PDU with GCC Conference Create Response.

  5. The RDP client sends an MCS Erect Domain Request PDU.

  6. The RDP client sends an MCS Attach User Request PDU.

  7. The RD Session Host responds with an MCS Attach User Confirm PDU.

  8. The RDP client sends multiple (in this case six) MCS Channel Join Request PDUs.

  9. The RD Session Host sends multiple (in this case six) MCS Channel Join Confirm PDUs.

  10. The RDP client sends a Security Exchange PDU.

  11. The RDP client sends a Client Info PDU.

  12. The RD Session Host sends a License Error PDU-Valid Client.

  13. The RD Session Host sends a Demand Active PDU.

  14. The RDP client responds with a Confirm Active PDU.

  15. The RDP client sends a Synchronize PDU.

  16. The RDP client sends a Control PDU-Cooperate.

  17. The RDP client sends a Control PDU-Request Control.

  18. The RDP client sends zero or more Persistent Key List PDUs. In this case, zero PDUs are sent.

  19. The RDP client sends a Control PDU-Font List PDU.

  20. The RD Session Host sends a Synchronize PDU.

  21. The RD Session Host sends a Control PDU-Cooperate.

  22. The RD Session Host sends a Control PDU-Granted Control.

  23. The RD Session Host sends a Font Map PDU.

For more details on steps 1 through 11, and 13 through 23, see [MS-RDPBCGR] section 1.3.1.1. For details on step 12, see [MS-RDPELE] section 1.3.3.

 
Show:
© 2015 Microsoft