Setting up the RDP Listener

This section describes how to setup RDP listener. To learn first steps of creating listener, please follow Creating a listener section.


  1. Go to Settings tab and press the RDP button in the Protocol field.

  2. Select the TLS enabled option to enable encryption.

  3. Check the NLA enabled option for additional security.

../../_images/6-0-listener-rdp.png

Note

Security mode must match the security mode setting in the RDP server configuration.


In case the TLS enabled option is chosen, select Legacy crypto option to allow negotiating older encryption algorithms (DSA(1024), RSA(1024)) when establishing RDP connections.

Selecting the RDP implementation

Starting with version 6.2, Fudo Enterprise handles RDP connections with a new implementation of the protocol, which additionally records the video stream sent by the server and the sound of the session. The previous implementation is still available and is selected per listener with the Use legacy RDP implementation option, placed under Legacy crypto.

Note

A newly created listener uses the new implementation - the Use legacy RDP implementation option is cleared by default. Listeners that already existed before the upgrade keep the option selected, so their behaviour does not change until you clear it.

Warning

The new implementation does not support three cases, and they behave differently:

  • Standard RDP Security, that is connections with the TLS enabled option cleared. Fudo Enterprise does not allow such a listener to be saved with Use legacy RDP implementation cleared, so the previous implementation is enforced here.

  • Kerberos authentication to the monitored server. This case is not enforced - select the Use legacy RDP implementation option yourself on such listeners, otherwise their connections will stop working.

  • Monitored servers that do not use the RDP graphics pipeline (RDPGFX), for example older systems. A session to such a server is ended with a message, because it could not be recorded. Select the Use legacy RDP implementation option on the listener used to connect to such servers.

Note

The new implementation records sessions only in the FBS format and does not produce a RAW dump. Recording options that ask for RAW have no effect on listeners that use it, and trusted timestamping, which operates on RAW files, is therefore unavailable for such sessions in version 6.2. See Trusted Timestamping.

Note

Recording the sound of a session and video recording are available only with the new implementation. Refer to the safe functionality options for the safe options that control them.

  1. Select Announcement option to enable it’s field and type in the notification that will be presented to the user on the login screen.

  1. In the Connection mode section, select desired connection mode.

Mode: bastion

Note

  • User connects to the target host by including name along with account login on the target server and target server address in the login string, e.g. john_smith#root#192.168.0.110.

  • For details on bastion connection mode, refer to Connection modes topic.

  • Select bastion button in the Connection mode field.

  • Select the IP address from the Local address drop-down list and enter port number.

  • Select External address option to enable its field and enter an IP address (or FQDN name) along with the port number, under which Fudo can be accessed from outside the local network.

Note

  • The Local address drop-down list elements are IP address defined in the Network configuration menu (Network Interfaces Configuration) or labeled IP addresses (Labeled IP Addresses).

  • Selecting the Any option will result in Fudo listening on all configured IP addresses.

  • When a Listener is configured with User Access Gateway as the local address, only one connection option is displayed after login to User Access Gateway for clarity, and the connection uses the address from the browser’s address bar together with the listener’s configured port.

  • In case of cluster configuration, select a labeled IP address from the Local address drop-down list and make sure that other nodes have IP addresses assigned to this label. For more information refer to the Labeled IP Addresses topic.

Mode: proxy

Note

User connects to the target host by providing Fudo Enterprise IP address and port number which unambiguously identifies target host.

  • Select proxy button in the Connection mode field.

  • Select the the IP address from the Local address drop-down list and enter port number.

Note

  • The Local address drop-down list elements are IP address defined in the Network configuration menu (Network Interfaces Configuration) or labeled IP addresses (Labeled IP Addresses).

  • Selecting the Any option will result in Fudo listening on all configured IP addresses.

  • When a Listener is configured with User Access Gateway as the local address, only one connection option is displayed after login to User Access Gateway for clarity, and the connection uses the address from the browser’s address bar together with the listener’s configured port.

  • In case of cluster configuration, select a labeled IP address from the Local address drop-down list and make sure that other nodes have IP addresses assigned to this label. For more information refer to the Labeled IP Addresses topic.

  • Select External address option to enable its field and enter an IP address (or FQDN name) along with the port number, under which Fudo can be accessed from outside the local network.

Note

The RDP config domain field can be used to define a custom hostname shown in the RDP client title bar for connections started from the User Access Gateway using the native RDP client. For a full configuration example, refer to Custom RDP Hostname in the Session Title.

  1. In the Server certificate field, click Generate certificate to generate TLS certificate by choosing key algorithm and providing Common Name (server name where the certificate is installed), or click Upload to upload server certificate file with private key pasted at the end of the file. The rest of the required fields will be filled automatically. Allowed format of the server certificate file is PEM, although besides .pem, accepted file extensions are .txt and .cert.

../../_images/5-4-listener-http-cert.png
  1. Click Save.


Note

The Server certificate is also used to sign the connection definition file that the User Access Gateway generates for the Native client option. Since the April 2026 Windows update, the Remote Desktop client verifies the signature of such files and warns the user when it is missing.

  • If the workstations trust the certificate, the user can dismiss the warning permanently by selecting Don’t ask again for connections to this publisher.

  • With a self-signed certificate the warning still appears, but the user can allow the publisher permanently.

  • A listener with no server certificate serves unsigned files, exactly as before.

  • The certificate is used only if it is currently valid and has the Server Authentication extended key usage. Otherwise the file is served unsigned and the event log shows the reason (FSW1710). A file signed with such a certificate would be rejected by the Remote Desktop client.

  • If the Local address is User Access Gateway, the address in the file is the name that the user typed in the browser to open the User Access Gateway. Such a file is signed only if the list of Access Gateway allowed hosts is filled and the name is on the list or is one of the node’s User Access Gateway addresses. The file then contains the name from the list. If the list is empty, which is the default, such files are not signed. To have them signed regardless of the name that the user typed, select the External address option of the listener.

  • The same applies to a listener that a Reverse Proxy publishes on 0.0.0.0 or :: without an external address. To sign its files, add the name that users type to reach the User Access Gateway through the Reverse Proxy to the list of allowed hosts, or set the external address in the listener mapping.

  • For a listener with TLS enabled, the User Access Gateway local address and no external address, the listener form shows whether the files will be signed.

  • Signing can be turned off for a safe with the Sign .rdp files option in the safe functionality settings.

To remove the warning entirely, use a certificate the workstations already trust.

Related topics: