Bug ID 899781: Custom dialup does not establish VPN

Last Modified: Mar 30, 2024

Affected Product(s):
APM-Clients APM(all modules)

Known Affected Versions:
11.6.5, 11.6.5.1, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 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, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6

Fixed In:
11.6.5.2

Opened: Apr 16, 2020

Severity: 3-Major

Symptoms

Attempting to establish a VPN using a custom dialup does not establish the connection, and reports an error: ...finished with code, -1073740512

Impact

WinLogon Integration/Custom dialup fails to establish VPN.

Conditions

-- Setup simple Network Access resource. -- Download the client package onto the client system and install it. -- Use WinLogon Integration/Custom dialup to establish VPN.

Workaround

Use EdgeClient or F5 Helper Applications to establish VPN.

Fix Information

WinLogon Integration/Custom dialup establishes VPN successfully.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips