[clug] Remote Desktop through a MS Terminal Server Gateway

Ian McLeod ianmcleod75 at gmail.com
Mon Aug 10 20:35:12 MDT 2009

I tried installing the XP RDP client using wine - runs fine - but no 
'advanced' options required to traverse a TS Gateway.  I tried copying 
across the mstsc.exe file from another XP machine verified as able to 
connect - to the WINE C Windows directory - and I receive an error when 
trying to run it that <lang_name>/mstsc.exe.MUI file can't be found or 

They don't make it easy, that's for sure.

Speaking of WINE - I presume I need to be just as careful with viruses, 
spyware etc when using WINE for Windows software as I would running a 
Windows machine?  Or should I run WINE apps as an unprivileged user or 

Daniel Pittman wrote:
> No.  That is some kooky RPC-over-SSL on the HTTPS port hack that Microsoft
> cooked up; it looks ugly, and is unrelated to the actual RDP stream that is
> used for display, so I think you are out of luck.
> [...]
> To save others the trouble: this isn't sufficient.  You need a specific
> "Terminal Services Gateway" protocol client to negotiate with the server
> before the normal RDP client — which is referred to here — can connect.
> On the plus side ... the TSG protocol is actually documented, and the details
> are freely available via MSDN without license[1], so if the OP wanted to
> implement a suitable client it /should/ be pretty easy.
> (Specifically, it should be possible to handle the negotiation in a separate
>  application, then execute rdesktop or some other client to handle the RDP
>  part, from my brief glance at it.)
> Given it is a fairly thin protocol I think it would only be a few days work to
> hack something together, possibly less if you can leverage the Samba work, or
> some other DCOM implementation on Linux.
> Regards,
>         Daniel
> Footnotes: 
> [1]  ...as far as I can tell.

More information about the linux mailing list