6.1.1.3 Connection Sequence between an RDP Client and a TS Server

Click here to view in the context of the full document

The diagram that follows illustrates one example of the messages that are exchanged between an RDP Client and a TSServer in an environment where no intermediary gateway is used.

f7f34ea8-b74a-48b2-a806-0c4aa357d254

Figure 22: Sequence illustrating RDP Client connecting to a TS Server

The connection sequence is described in the following steps.

  1. The RDP Client initiates a connection to the TS Server by sending an X.224 Connection Request protocol data unit (PDU), as described in [MS-RDPBCGR] section 1.3.1.1.

  2. The TS Server 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 TS Server 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 server 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 TS Server 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 TS Server sends a License Error PDU – Valid Client. Note that there are several possible scenarios for the licensing negotiations (as described in [MS-RDPELE] section 1.3.3). For this scenario it is assumed that a valid, non-expired license exists for the client on the License Server.

  13. The TS Server 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 TS Server sends a Synchronize PDU.

  21. The TS Server sends a Control PDU – Cooperate.

  22. The TS Server sends a Control PDU – Granted Control.

  23. The TS Server sends a Font Map PDU.

Post Connection:

After the client receives the Font Map PDU, it can start sending mouse and keyboard input to the server, and upon receipt of the Font List PDU the server can send graphics output to the client.

 

Click here to view in the context of the full document

Show: