MSTSC Remote Program Desktop login for C # development

 Publicaxmstsclib.axmsrdpclient rdpclient; Rdpclient=Newaxmstsclib.axmsrdpclient (); Rdpclient.dock=DockStyle.Fill; Rdpclient.width= Screen.PrimaryScreen.Bounds.Width;//Control WidthRdpclient.height = Screen.PrimaryScreen.Bounds.Height;//Control Width             This.               Controls.Add (rdpclient); Rdpclient.server= This. StrIP;//Server AddressRdpclient.username = This.               StrName; RdpClient.AdvancedSettings2.RDPPort=3389; RdpClient.AdvancedSettings2.ClearTextPassword= This. Strpwd;//PasswordRdpclient.colordepth = -;//number of color bitsRdpclient.fullscreen =true;//whether full screenRdpclient.connect (); 

Understanding Remote Desktop Protocol (RDP)
< type= "Text/javascript" >

Remote Desktop Protocol (RDP) for communication between the Terminal server and the Terminal Server client. RDP is encapsulated and encrypted in TCP.

The Remote Desktop protocol is based on and is the Protocol standard for the extended T 120 series. Multichannel support protocols are used for individual virtual channel-stored presentation data, serial device communication, authorization information, high-encryption data (keyboard, mouse activity), and more. Because RDP is an extension of the core T.share protocol, multiple other features will remain as part of the functionality required for RDP, such as the architecture to support multipoint (multiparty sessions). Multipoint data transfer allows data to be sent from the application in "real-time multiparty delivery without having to send the same data to each session of a separate (for example, virtual whiteboards).

Windows Terminal Server In this first version however, we will centrally provide reliable and fast point-to-point single session communication. Only one data channel will be available in the originally released Terminal Server 4.0 However, the flexibility of RDP offers a lot of functionality in the future of the product space.

One reason Microsoft has decided to implement RDP connections for Windows NT Terminal Server is that it provides a very extensible foundation for generating many more features. This is because RDP is used for data transmission 64,000 independent channels. However, the current transfer activity uses only a single channel (for keyboard, mouse, and presentation data).

Also, RDP is designed to support many different types of network topologies (such as ISDN, POTS, and multiple LAN protocols such as IPX, NetBIOS, TCP/IP, and so on). The current version of RDP will only run on TCP/IP, but Additional protocol support for customer feedback can be added in future releases.

Participating in sending and receiving data through the RDP stack activity is essentially the same as the seven layer OSI model standard public LAN network now. The data is transferred from the application or service through the protocol stack sectioned, directed to a channel (via MCS), encrypted, wrapped, framed, packaged into the network protocol and finally resolved, and the cable is routed to the client. The data returned in the same way is only valid in reverse, using its address that the packet is stripped of, and then unwrapped decrypted, and so on until the data is available to the application for use. The Protocol Stack modification key section takes place between fourth and seventh layers, where data is encrypted, wrapped and framed, directed to a channel, and the prioritization level is determined.

One of the key points for application developers is that using Rdp,microsoft has an abstraction that immediately handles the complexity of the protocol stack. In this way, they only need to write clean, well-designed, good 32-bit applications and the RDP stack is responsible for the rest of the work by the Terminal server and its client connections.

For more information about how applications interact on a terminal server and about developing applications for the Windows Terminal Server infrastructure, review the "optimizing Windows NT Server 4.0, Terminal Server Edition Applications" white paper. It is worth discussing that the four components in an RDP stack instance are multipoint Communication services (MCSMUX), Generic conferencing control (GCC), Wdtshare.sys, and Tdtcp.sys. Both Mcsmux and GCC are in the International Telecommunication Union (ITU) T 120 series. MCS consists of two standards: it defines the t.122 of the multipoint service and the t.125 of the specified data transfer protocol. Mcsmux the data that is sent by the assignment, priority, and fragmentation of the control channel (multiplexing data to predefined virtual channels in the protocol). Essentially, extract multiple RDP stacks to a single entity from that GCC angle. GCC is responsible for managing these multiple channels. The GCC allows the creation and removal of session connections and control resources to provide MCS. Each Terminal Server protocol (currently, the only RDP and Citrix ICA support) will have a protocol stack instance loaded (waiting for the connection to request a listener stack). The Terminal Server device driver coordinates and manages the RDP protocol activity and the RDP driver (Wdtshare.sys) for smaller components, UI transport, compression, encryption, frames, and so on, and the Transport Driver (Tdtcp.sys) is packaged into the underlying protocol network TCP/IP protocol.

RDP is a fully independent foundation of the transport stack, developed in TCP/IP for this case. The RDP on a fully independent transport stack, expressed as the basic part of their customers need to add little or no significant change to the protocol we can also additional transport drivers for additional network protocols. These are the key elements of RDP performance and extendibility on the network.

MSTSC Remote Program Desktop login for C # development