The sonicwall has no DHCP or DNS services enabled, it just sends its traffic to our Windows server that runs DHCP and DNS on 192.168.1.XXX. DHCP is enabled on the modem, and that issues a local address of 10.1.10.9 to the Sonicwall. The modem connects only to the Sonicwall. More details on the network setup that may be useful: No ports are being blocked at the modem level as far as i can tell, but that traffic just isn't getting through. No settings have been changed on the firewall, but under the new modem, people can no longer connect.
The dell sonicwall SSL-VPN is configured to run on port 4433 (the default). Here's how the NetExtender app was previously used to connect:īut now when people hit connect, it pops up that error message from above, so the Server address must not actually be handing off? The server may be down or your internet settings may be down. The client PCs can no longer connect over the VPN- the NetExtender app pops up with the message: Error: The server is not reachable. We have a static IP business connection from Comcast, and a few weeks back the box crapped out. Once the user has completed the OTP set up the User will appear under the SonicWall/Users/Local Users section (don’t deleted this as it is keeping all the relevant information regarding their OTP).Īttachment: Setting_up_the_TOTP_on_SonicWall_UTM_appliances_Google_or_other_Authenticators.So we have a Dell Sonicwall unit that serves as our firewall and also runs the VPN functionality via the Sonicwall SSL-VPN and the accompanying client side application, Sonicwall NetExtender.
For the first time this is probably best done on a pc so the user can scan the barcode from the screen if not they can use the Text Code method and copy and paste from the mobile browser in to their chosen authenticator.