The SonicWall authenticates all users as soon as they attempt to access network resources in a different zone (such as WAN, VPN, WLAN, etc.), which causes the network traffic to pass through the SonicWall. Users who log into a computer on the LAN, but perform only local tasks are not authenticated by the SonicWall.

Feb 20, 2018 Configuring the Dell SonicWALL Appliance for LDAP Currently it is only used for a user connecting via L2TP with the SonicOS L2TP server. In the future this may also be supported for Global VPN Client. In Active Directory the static IP address is configured on the Dial-in tab of a user’s properties. LDAP authentication for SonicWALL VPN - Server Fault Now, before your logins will work you have to go to the Directory tab and click “Auto-configure.” If auto-configure fails, make sure the SonicWALL’s LDAP username and password (e.g. sonicwall_ldap@OURDOMAIN.local) is correct. Configuring Local Users on Users > Local Users - SonicWall NOTE: The VPN access tab affects the ability of remote clients using GVC, NetExtender, and Virtual Office bookmarks to access network resources. To allow GVC, NetExtender, or Virtual Office users to access a network resource, the network address objects or groups must be added to the “allow” list on the VPN …

SonicWALL SSL-VPN 4000 - Active directory integration

L2TP VPN WIndows 10 SonicWall w/domain. Mapped drives May 21, 2020

Object - In LDAP terminology, the entries in a directory are referred to as objects. For the purposes of the SonicOS implementation of the LDAP client, the critical objects are ‘User’ and ‘Group’ objects. Different implementations of LDAP can refer to these object classes in different fashions, for example, Active Directory refers to the user object as ‘user’ and the group object

Configuring Users for SSL VPN Access - SonicWall