If the pool is too small and all addresses are in use or reserved, it is expected behavior that the SonicWALL doesn’t respond. Make sure you have sufficient addresses left in the address pool. Sonic is NOT DHCP enabled, whart is checked is forward all requests to the server addresses below with DHCP server on local LAN in there.Rebooting will fix that behavior at once. SonicWALLs are pretty stable but we’ve seen it a couple of times that the DHCP server is acting strange, as if all IP addresses are reserved, yet that’s not what you will see in the web interface. The DHCP protocol is designed in such a way that there can be multiple DHCP servers per network and only those who think they can fulfill a request will also respond to it, all others will stay silent (there is no “negative” response for discover requests). From the Interface drop-down menu, select the interface to be used for SSL VPN services.
Navigate to the SSL VPN > Client Settings page. The SonicWALL doesn’t want to reply to your DHCP request. To configure the SSL VPN Client Address Range: 1.Please see this FAQ entry for more details.
Click on the configure button for central gateway, DHCP over VPN configuration windows is displayed. That would be the case if there is an issue with the VPN tunnel itself not working properly. Navigate to MANAGE VPN DHCP over VPN ,Make sure that central gateway is selected. The SonicWALL never received your DHCP request (DHCP-Discover).Once the VPN tunnel itself has already been established, the VPN client must perform a DHCP exchange to obtain an IP address and use this IP address for all traffic sent over the VPN tunnel. SonicWALLs distribute IP addresses using the DHCP protocol.