Skip to main content

Known Issues with RDP Connections

Known issue: RDP connection return with error "The connection transport layer failed" after upgrade to version Eggplant Gateway v26.2.6 onwards​

Issue: When trying to connect to Windows SUT via RDP connection, connection failed with error "The connection transport layer failed".

Fix: Check the EPGW logs to identify the error contains "Error: SSL_NOT_ALLOWED_BY_SERVER". Go through below configuration to enable SSL in Windows SUT:

  • Enable SSL for gpedit.msc → Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Security -> Require use of specific layer for remote (RDP) connections -> Enabled -> choose SSL for Security Layer

Known issue: RDP Connection Keyboard Layout When Running via Windows Service​

Issue: When EPGW is called through a Windows Service, such as the DAI Run Agent service, the keyboard layout detected by EPGW RDP and synchronized with the SUT may not match the keyboard layout configured for the user. This issue occurs regardless of whether the Windows Service runs under the LocalSystem account or a user account. The keyboard layout is obtained from the system locale instead of the keyboard layout configured in the user's settings.

Workaround: When the Run Agent needs to run as a Windows Service, ensure that the Welcome screen/system accounts locale and keyboard settings are configured to match the desired keyboard layout for the test environment.

Last updated on