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.
We have a static IP business connection from Comcast, and a few weeks back the box crapped out. A tech came out and replaced the box. Now though, the VPN has stopped working. The client PCs can no longer connect over the VPN- the NetExtender app pops up with the message:
Error: The server is not reachable. The server may be down or your internet settings may be down.
Here's how the NetExtender app was previously used to connect:
But now when people hit connect, it pops up that error message from above, so the Server address must not actually be handing off?
The dell sonicwall SSL-VPN is configured to run on port 4433 (the default). No settings have been changed on the firewall, but under the new modem, people can no longer connect.
No ports are being blocked at the modem level as far as i can tell, but that traffic just isn't getting through.
More details on the network setup that may be useful: The modem connects only to the Sonicwall. DHCP is enabled on the modem, and that issues a local address of 10.1.10.9 to the Sonicwall.
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. Local devices are given address on this 192.168.1.100+ pool.
The sonicwall VPN is configured to issue an address between 192.168.1.70 & 192.168.1.80 to clients.
Nothing has changed on the configuration side of the Sonicwall or the Windows server (DHCP and DNS), and I noticed the problem a few days after the new modem was put in. This makes me think the problem lies with the modem's configuration. Do I need to do a port forward or something at the modem level? Should DHCP be disabled on the modem?
I'm not the person who originally set all this up, and my networking knowledge is pretty weak so I was hoping one of you smart people might see where I'm going wrong?