Microsoft remote desktop protocol driver#
Microsoft remote desktop protocol windows#

a transport driver (Tdtcp.sys) to package the protocol onto the underlying network protocol, TCP/IP.

an RDP driver (Wdtshare.sys) for UI transfer, compression, encryption, framing, and so on.

The Terminal Server device driver coordinates and manages the RDP protocol activity. Each Terminal Server protocol (currently, only RDP and Citrix's ICA are supported) will have a protocol stack instance loaded (a listener stack awaiting a connection request). The GCC allows the creation and deletion of session connections and controls resources provided by MCS. GCC is responsible for management of those multiple channels. It essentially abstracts the multiple RDP stacks into a single entity, from the perspective of the GCC.

channel assignment by multiplexing data onto predefined virtual channels within the protocol.

T.125: It specifies the data transmission protocol.

T.122: It defines the multipoint services.

MCSmux and GCC are part of the International Telecommunication Union (ITU) T.120 family.

the Multipoint Communication Service (MCSMUX).

Microsoft remote desktop protocol windows#

Then the RDP stack implemented by the Terminal Server and its client connections takes care of the rest.įor more information about how applications interact on the Terminal Server, and what to know when developing applications for a Windows Terminal Server infrastructure, see the following white paper: Optimizing Applications for Windows NT Server 4.0, Terminal Server Editionįour components worth discussing within the RDP stack instance are: It allows them to write clean, well-designed, well-behaved 32-bit applications. One of the key points for application developers is that, in using RDP, Microsoft has abstracted away the complexities of dealing with the protocol stack. Key portions of the protocol stack modifications occur between the fourth and seventh layers, where the data is: Finally the data is presented to the application for use. The packet is stripped of its address, then unwrapped, decrypted, and so on. The returned data works the same way only in reverse. It's sectioned, directed to a channel (through MCS), encrypted, wrapped, framed, packaged onto the network protocol, and finally addressed and sent over the wire to the client. Data from an application or service to be transmitted is passed down through the protocol stacks. The activity involved in sending and receiving data through the RDP stack is essentially the same as the seven-layer OSI model standards for common LAN networking today. With customer feedback, other protocol support may be added in future versions. The current version of RDP will only run over TCP/IP. RDP is also designed to support many LAN protocols, such as IPX, NetBIOS, TCP/IP. RDP is designed to support many different types of Network topologies, such as ISDN, POTS. However, current transmission activities are only using a single channel (for keyboard, mouse, and presentation data). RDP provides 64,000 separate channels for data transmission. One reason that Microsoft decided to implement RDP for connectivity purposes within Windows NT Terminal Server is that it provides an extensible base to build many more capabilities. However, the flexibility of RDP gives plenty of room for functionality in future products. Only one data channel is used in the initial release of Terminal Server 4.0. In this first release of Windows Terminal Server, we're concentrating on providing reliable and fast point-to-point (single-session) communications.

It doesn't require to send the same data to each session individually. Multipoint data delivery allows data from an application to be delivered in real time to multiple parties, such as Virtual Whiteboards.

Several other capabilities are retained as part of the RDP, such as the architectural features necessary to support multipoint (multiparty sessions). RDP is an extension of the core T.Share protocol. highly encrypted data, such as keyboard, mouse activity.A multichannel capable protocol allows for separate virtual channels for carrying the following information: RDP is based on, and is an extension of, the T-120 family of protocol standards. RDP is encapsulated and encrypted within TCP.Īpplies to: Windows Server 2012 R2 Original KB number: 186607 Summary This article describes the Remote Desktop Protocol (RDP) that's used for communication between the Terminal Server and the Terminal Server Client.