Recently we have seen that there is an issue with L2TP in combination with the 4.35 (patch 2) firmware. The issue consists that Local User or Users authenticated with an external Active Directory server, cannot build an L2TP tunnel to the firewall.
How can this be?
The check mechanism is changed from 4.33 and 4.35 because there have been some updates on the RADIUS daemon. An incomplete RADIUS configuration affects the radius daemon. Therefore we need to enter some values in the Radius screen
A workaround, for now, is to configure settings as below:
Server Address: 127.0.0.1
Authentication Port: 1812
We are working in the meanwhile on a permanent fix.