A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/14 07:35 Browser : Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 Iceweasel/26.0 IP-Address : 134.245.254.47 Hostname : m-047.informatik.uni-kiel.de Old Revision: https://wiki.x2go.org/doku.php/wiki:advanced:tce:directrdp?rev=1397458830 New Revision: https://wiki.x2go.org/doku.php/wiki:advanced:tce:directrdp Edit Summary: User : sunweaver @@ -15,29 +15,39 @@ === How it works in detail === If X2Go Client is used for proxying an RDP session, the session start up goes like this: - o an X2Go Client machine connects to an X2Go Server - o On this X2Go Server the '''rdesktop''' is installed - o From this X2Go Server the MS Windows machine (Terminal Server or Workstation) can be reached (maybe on some internal network) - o X2Go Client launches an X2Go Session and calls the '''rdesktop''' command inside this session (with a special set of parameters) - o The '''rdesktop''' RDP client connects to the MS Windows machine, starts/resumes an RDP session there - o The RDP client's Windows desktop window appears inside the X2Go Session - o Whatever appears in the X2Go Session gets displayed on the X2Go Client machine - o the X2Go Client can now work on an MS Windows machine + * an X2Go Client machine connects to an X2Go Server + * On this X2Go Server the '''rdesktop''' is installed + * From this X2Go Server the MS Windows machine (Terminal Server or Workstation) can be reached (maybe on some internal network) + * X2Go Client launches an X2Go Session and calls the '''rdesktop''' command inside this session (with a special set of parameters) + * The '''rdesktop''' RDP client connects to the MS Windows machine, starts/resumes an RDP session there + * The RDP client's Windows desktop window appears inside the X2Go Session + * Whatever appears in the X2Go Session gets displayed on the X2Go Client machine + * the X2Go Client can now work on an MS Windows machine === Benefits of X2Go-proxied RDP Sessions === There are some benefits gained from this approach compared to direct RDP session setups. - o Traffic between server/client is always encrypted via SSH - o On low bandwidth lines, an X2Go-proxied RDP Session might scale better than the native RDP protocol - o The proxying X2Go Server can be used as a firewall pass-through gateway and you can connect to machines behind that firewall - o All SSH-related extra authentication features (SSH pubkey/privkey, OTP authentication, GPG-SmartCard authentication, etc.) can be used for the connection to the proxying X2Go Server (i.e. double secure your network) + * Traffic between server/client is always encrypted via SSH + * On low bandwidth lines, an X2Go-proxied RDP Session might scale better than the native RDP protocol + * The proxying X2Go Server can be used as a firewall pass-through gateway and you can connect to machines behind that firewall + * All SSH-related extra authentication features (SSH pubkey/privkey, OTP authentication, GPG-SmartCard authentication, etc.) can be used for the connection to the proxying X2Go Server (i.e. double secure your network) === Session Setup for X2Go-proxied RDP Sessions === - TODO + {{ :wiki:advanced:tce:x2go-proxied-rdp.png?300|}} + + In X2Go Client's session profile manager, select the following parameters: + + * profile name: a descriptive name for that session profile + * hostname: the hostname of the RDP-proxying X2Go Server + * username: username on the RDP-proxying X2Go Server + * SSH authentication features: if appropriate, select a private SSH key, enable agent based authentication or use GSSAPI + * Session Type: //Connect to Windows terminal server// + * Session options: Server: IP address of the MS Windows machine + * Advanced options...: '''-u <windows-username> -d <windows-domain-name>''' ==== Direct/Native RDP Sessions ===== -- This mail was generated by DokuWiki at https://wiki.x2go.org/