
I think I get this if I mistakenly write the server address in wrong format or with wrong port. Can you move closer or even hardwire in with a Ethernet cord to see if you can get a better connection? Your daily dose of tech news, in brief. Otherwise, you can try to use 444 as the SSLVPN port and check if that solves the problem. 1 22:50:29, Receive SvcMsg : 265, wParam = 1308624, lParam = 1, content length = 0 The click here at the top of the page has the most current version. 1 22:39:48, Receive SvcMsg : 266, wParam = 0, lParam = 0, content length = 0 Read these next. If she can't I would hunt to see if she can access other sites and if she has any kind of filtering software or other firewall running that would be new (since the problem started). Using the most recent NetExtender 8.0.241 from mysonicwall, it asked me to accept the certificate, to which I selected "Always Trust", and then it says "The server is not reachable.

1) X1 interface settings user login check box must enable. Licenses can be purchased for anything from 1 year to bundles of over 1. This makes me think the problem lies with the modem's configuration.Disconnected,RAS has encountered an error. 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. The sonicwall VPN is configured to issue an address between 192.168.1.70 & 192.168.1.80 to clients. Local devices are given address on this 192.168.1.100+ pool. 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. 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.
