In RDP's connection sequence, which phases fix and join the static virtual channels, and what must finish before graphics flow?
answer
- ten phases, in a set order
- the channel list is asked for early
- joining comes one phase later
- capabilities precede finalization
basics
~20 sThe client requests its static channels in the basic settings exchange and joins them in the channel connection. Input starts after Confirm Active and graphics after the Font List PDU, both late in the sequence.
solid answer
~40 sMS-RDPBCGR describes ten phases: connection initiation (X.224 request and confirm), basic settings exchange, channel connection, RDP security commencement, secure settings exchange, optional connect-time auto-detection, licensing, optional multitransport bootstrapping, capabilities exchange, and connection finalization. The **basic settings exchange** carries the MCS Connect Initial and Response with GCC data, including the requested static channel names. The **channel connection** then runs Erect Domain and Attach User and sends a Channel Join for the user channel, the I/O channel and every static channel. Once the client has sent Confirm Active in answer to Demand Active, it can send input; once the server receives the Font List PDU, it can send graphics. Channel data does not flow until the whole sequence is complete.
go deeper
Know there is an ordered connection sequence and that settings and channels are agreed before any screen appears.
Name the phases in order, say which one requests the static channels and which one joins them, and place Demand Active and Confirm Active.
Use the phase names to localise a failed or stalled connection and to read a capture.
Treat the sequence as the point where policy decisions about security and channels become fixed for the connection.
## The ten phases and what each one settles MS-RDPBCGR section 1.3.1.1 (version dated 9 March 2026) divides the connection sequence into ten phases. The useful way to remember them is by the question each answers. | # | Phase | What it settles | |---|---|---| | 1 | Connection initiation | The X.224 Connection Request and Confirm carry the security protocols the client offers and the one the server selects | | 2 | Basic settings exchange | MCS Connect Initial and Response, carrying GCC data blocks: core, security and network data, including requested static channels | | 3 | Channel connection | Erect Domain, Attach User, then a Channel Join for the user channel, the I/O channel and every static channel | | 4 | RDP security commencement | Only when Standard RDP Security with encryption is in force: a Security Exchange PDU and session keys | | 5 | Secure settings exchange | The Client Info PDU, which carries the user name, the password and the auto-reconnect cookie | | 6 | Optional connect-time auto-detection | Round-trip latency and bandwidth of the link | | 7 | Licensing | Transfer of a license from server to client, where the mechanism requires one | | 8 | Optional multitransport bootstrapping | Whether an additional transport such as UDP is set up | | 9 | Capabilities exchange | Demand Active from the server, Confirm Active from the client | | 10 | Connection finalization | Synchronize, control and font PDUs exchanged in both directions | Use these names rather than numbers when you speak about them; the numbering is a reading aid. ## Where the channels are fixed Two phases matter for channels. - **Basic settings exchange.** The static virtual channels are requested and confirmed here. The request names up to 31 channels in the network data block; the response returns the channel identifiers. - **Channel connection.** The endpoints are joined here. The client attaches its user identity, then sends a Channel Join Request for the user channel, the I/O channel and each static channel, and the server confirms each. Some client versions send these one at a time, waiting for each confirmation; others (RDP 8.1, 10.0 and 10.1 clients) send them in a single batch to shorten the sequence. MS-RDPBCGR is explicit that once joined, the endpoints do not exchange channel data until the connection sequence is complete. That is why a clipboard or drive channel can exist in the channel list yet be silent until finalization finishes. ## Security wraps the sequence The plain RDP connection sequence does not authenticate the server. The security-enhanced sequence addresses that: the client appends a negotiation request to the X.224 Connection Request, the server selects a package in its Confirm, and after that the handshake of the chosen package runs and all later RDP traffic is secured with it. The channel list is therefore sent after the negotiation and the chosen package's handshake. How that negotiation is chosen and what each protocol offers is covered with the encryption and TLS material, not here. ## When input and graphics start - Once the client has sent the **Confirm Active PDU**, it can start sending mouse and keyboard input. - Once the server receives the **Font List PDU**, it can start sending graphics output. - Client-to-server PDUs in finalization (Synchronize, Control Cooperate, Control Request Control, optional Persistent Key List, Font List) have no dependency on server-to-client PDUs and can be sent as one batch. ## Reactivation After the sequence completes, the server can send a Deactivate All PDU. That means either the connection will be dropped or a capability re-exchange will occur, in which case the capabilities exchange and connection finalization are run again. This is how a running session can renegotiate without a new connection. ## Why a practitioner cares - **Troubleshooting.** A stall before the capabilities exchange points at security negotiation, settings, channels, credentials or licensing; a stall after it points at the session itself. Mapping the symptom to a phase narrows the search. - **Reading a capture.** The phase names tell you what each PDU is for, so you can place a stall: waiting for Channel Join Confirm is different from waiting for Demand Active. - **Redirection.** The channel list is requested early, so a static channel the client did not request cannot be used in that connection. ## Common mistakes - Saying channels are joined in the same phase in which they are requested. - Placing licensing or capabilities before the channel connection. - Thinking the password is sent in the X.224 request. - Assuming input and graphics start together at the same PDU.
- Which phase is skipped unless Standard RDP Security is in use, and what does it add?RDP security commencement. If Standard RDP Security is in force with encryption, the client sends a Security Exchange PDU containing an encrypted 32-byte random number, and both sides derive session keys from it and the server's random number. With the security-enhanced sequence this phase does not occur because the negotiated package secures the traffic.
- What does a Deactivate All PDU after the sequence has finished mean?It signals that the connection will be dropped or that a capability re-exchange will occur. In the re-exchange case the capabilities exchange and connection finalization phases are executed again on the same connection. It is not the same as a user-initiated disconnect.
- Says channels are requested and joined in the same phase
- Believes input and graphics begin at the same PDU
- Thinks the password travels in the X.224 Connection Request
- Puts the capabilities exchange before the channel connection
- Treats RDP security commencement as part of every connection