I suggest keeping a local user setup in the event the RADIUS server(s) go down unexpectedly.) Go to Users -> Settings and change User Authentication method from “Local Users” to “RADIUS + Local Users” (this allows you to use either local user accounts created in the SonicWALL OR use Active Directory based user accounts during authentication. Configure SonicWALL for RADIUS authentication Step 1 – Change User Authentication mode Make sure the Access Granted radio button is selected for the Permission properties, and use the default selections for Authentication Methods, Configuration Constraints, and Configuration Settings, then select Finish in the Add Network Policy wizard. Specific the “SSL-VPN Access” global group you previously created in Active Directory. Add the condition Windows Groups, and click ADD. Step 4 – Create New Network Policy in NPSĬreate a new Network Policy and call the policy, “ SonicWALL SSL VPN“. In Active Directory, create a global group called “SSL-VPN Access” and add the applicable users to this group that will require remote VPN access.
Configure Windows Server for RADIUS authentication Step 1 – Install NPSĪdd the Network Policy Server role on your Windows server if it’s not yet already installed.Īdd a RADIUS client to NPS using the LAN IP address of the SonicWALL firewall, and create an applicable Shared Secret password.
The following article is a step by step guide how to configure the firewall and Windows Servers to accomplish this. Setting up the SonicWALL firewall for using SSL VPN is pretty simple, even when it comes to utilizing Windows Domain Accounts via RADIUS authentication.
0 kommentar(er)
