Bug ID 558850: Client can not connect to Windows 10 using ActiveX RDP client launched from the APM Webtop if "Allow connections only from computers running Remote Desktop with Network level Authentication" is disabled.

Last Modified: Mar 12, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4

Opened: Nov 18, 2015
Severity: 3-Major

Symptoms

Client can not connect to Windows 10 using ActiveX RDP client launched from the APM Webtop if "Allow connections only from computers running Remote Desktop with Network level Authentication" is disabled at the remote host. The user is shown an error message: "The connections cannot proceed because authentication is not enabled and the remote computer requires that authentication be enabled to connect."

Impact

Client can not connect to remote server

Conditions

Remote server is Windows 10, "Allow connections only from computers running Remote Desktop with Network level Authentication" is not enabled on the server

Workaround

Several workarounds are available here: 1) Enable "Allow connections only from computers running Remote Desktop with Network level Authentication" on the remote server 2) Edit the registry on the remote or deploy as GPO to your desktop: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp] "SecurityLayer"=dword:00000001 "UserAuthentication"=dword:00000000 3) Using RDG may be considered as yet another possible workaround.

Fix Information

None

Behavior Change