Last adaptation to the version: 14.2.0 (07.2026)
- Beta For participants on the Beta Channel only:
- VPN hosts can be copied
- Extended search function available
- Additionally: display of the security setting used in the overview
- When configuring a connection, user groups can be selected directly and displayed in the table 14.1.1
- The overview table of the CVPN connections has been extended with numerous pieces of information 14.1.1
- The selectable video resolutions have been increased 14.1.1
Introduction
UTMuser@firewall.name.fqdn VPN
Clientless VPN provides the ability to connect to an RDP or VNC server on the corporate network via the browser. Users log in to the user interface and are then given the option to connect with a designated server. For this to work, the browser must have HTML5, Java or similar is not necessary.
The overview displays numerous pieces of information:
- Server name
- Type
- IP address
- Port
- Domain
- User name
- Video mode
- Security
TLS Indication of the securityRDP (deprecared) Warning for outdated protocols or unencrypted connections
- User groups
CVPN-User Assigned group with Clientless VPN permissionCVPN-User Assigned group without Clientless VPN permission
| Spalte | Name der Spalte auswählen. Die Auswahl hängt von der Tabelle ab, in der man sich gerade befindet. | |
| Suchbegriff | Begriff, nach dem in der ausgewählten Spalte gesucht werden soll | |
| Kriterien mit ... -Operator verbinden |
/ | Suchbegriffe verknüpfen mit und bzw. oder. Es müssen entweder alle Begriffe vorkommen oder einer |
| Weiteren Begriff in einer Spalte hinzufügen für eine Suche nach mehreren Kriterien | ||
| Suche starten | ||
| Suche starten und erweiterte Suche zuklappen |
The following actions are available:
- notemptyNew as of v14.2.0
Copy VPN host - Edit
- Delete
Configuration of the UTM
Add Clientless Host
Under click the button.
All servers that are to be made available to users via the user interface using Clientless VPN are entered here.
Group permission
UTMuser@firewall.name.fqdn Authentication User
- Click Area Groups button or existing group
- in the Permissions section:
- Enable Userinterface with the On button
- Enable Clientless VPN with the On button
- Assign a unique name in the Group name: field.
Subsequent assignment of the group

- Switch to the Clientless VPN tab.
- Activate desired clientless VPN connection with On
- Apply the changes with
Allow access
UTMuser@firewall.name.fqdn Firewall
Now it must be ensured that the clientless VPN user is also allowed to log in to the user web interface via the browser. This can be done either by Implicit Rules or by manually creating a corresponding Packetfilter Rule on the interface.
In this case it is sufficient to activate the User Interface Portal VPN rule with On in the menu under Area VPN.
Apply CVPN
Login to the user interface
- The user login to the user interface is called up via the IP address or URL of the UTM, possibly followed by a port specification
- Depending on the assigned permissions, various functions are made available
- Click on the corresponding tile to access the desired function
| Configured | Port | Example call with IP | Example call with URL |
|---|---|---|---|
| Default | 443 | i.e. https://192.168.175.1 | i.e. https://utm.ttt-point.de |
| Port changed bei administrator Menu: Network / Appliance Settings / Appliance Settings / Webserver / User Webinterface Port |
4443 | i.e. https://192.168.175.1:4443 | i.e. https://utm.ttt-point.de:4443 |
After entering the IP address, the user login page of he Securepoint UTM is loaded. The login credentials are entered there.
Start CVPN
Run CVPN
Hints
Windows 2012R2 with enabled terminal services

If a 2012R2 server is to be used as the RDP server for the clientless VPN, the establishment of the RDP connection fails due to the "Authentication at network level".
When using the terminal services, this function can also no longer be deactivated via the familiar way.
However, it is possible to force the disabling of ""Authentication at network level"" via the GPO (Group Policy).
Adjusting the registry
However, it may also be necessary to adjust a registry entry. This must have a value of 1.
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
SecurityLayer






