Thincast RD Gateway protects all RDP traffic outside the company network by establishing a secure SSL tunnel between the end-user's device and the RD Gateway server. HTTPS is widely available, standard and easy to use with an existing infrastructure.
Extended access control policies allow fine-grained control on the user level.
- Client policies allow you to define where a client is allowed to connect from and which RDP extensions, for example drive redirection, are allowed for this user.
- Server policies allow you to define to which internal server a connection is allowed.
RD Gateway protects your infrastructure against RDP brute-force or similar attacks since the RDP ports of the company servers are no longer exposed on the internet. HTTP authentication over a secure SSL tunnel is used before access to the internal RDP server is allowed.
RD Gateway comes with a variety of licenses and plans for any company size and project. There are licences available for 10, 25, 50 and 100 concurrent users. Contact our sales team for an unlimited license.
Platforms and Domain integration
RD Gateway supports Microsoft Server and Microsoft Workstation operating systems. To integrate seamlessly into an existing Microsoft domain infrastructure, Thincast RD Gateway offers full Microsoft Active Directory integration.
Thincast RD Gateway uses standardized protocols and technology. This means you can easily integrate or combine it with other software that conforms to these standards.
Supported operating systems
- Windows 7 / 8 / 8.1 / 10
- Windows Server 2008 R2 / 2012 / 2012 R2 / 2012 / 2016 / 2019
ArchitectureThincast RD Gateway supports x86 and x64 environments.
Memory and storage
The minimum memory required on the host system is 64 MB, but 128 MB and above is recommended. Thincast RD WebService needs at least 32MB of available disk space for the application. If you have enabled access login, this amount can increase depending on your number of active connections.
Trustworthy SSL-certificate on the client and server.
The certificate name (CN) has to be identical with the DNS name which the RDP client uses to establish a connection to the RD Gateway Server.
Remote Desktop ClientRDP protocol version 6 and above supported.
If you wish to have more than 100 connections or are interested in a custom licensing plan, please contact us and we will be in touch.
Should you experience any issues with Thincast Workstation or have other support questions, please use our contact form.
In certain cases, Thincast Support might request a TSRP (Thincast Support Request Package) from you to analyze your problem.
In these cases please follow the instructions from our Thincast Support engineers.