also, If you fire up the 'X' VPN first, they could block VPN over VPN. You can temporary set/reset them with a lower metric and probably could get it working. If its not solving the issue permanently with above steps, Try to install Sonicwall Mobile connect. Once it done the hardware changes try to use the NetExtender. Next time you want to play with this, fire it up and do the 'route print' to see those changes. Navigate to Windows Device Manager -> Network Adaptores and uninstall the WAN Miniport (IP) and WAN Miniport (PPTP) devices, then scan for the hardware changes. Can Sonicwall Mobile or GVC client figure it out, no really because it just expects 0.0.0.0 to be routed out the physical ethernet or wifi device with a proper metric.

Now, the PC does not know to route over the Sonicwall Virtual adaptor to get to 10.1.1.x. Trouble is, there is a route already in place with a lower metric for 0.0.0.0. What I did try and troubleshoot was to add a static route in the Sonicwall to the 172.20.55.0/24 network, and that stopped the tracert straight after the client address, rather than. Now, if you try to startup a VPN for sonicwall, that will create a route for the local LAN. What I can't do though is ping the address from a client using the Netextender, despite me seeing the Netextender client has picked up the client route i've added. If you do a 'route print' from the command line, you can see this. This says 'all traffic, go out virtual network 1'. The top industry researching this solution. SonicWall Netextender is most commonly compared to SonicWall Mobile Connect: SonicWall Netextender vs SonicWall Mobile Connect. IT Central Station users give SonicWall Netextender an average rating of 8 out of 10.

This VPN is for all traffic so the local firewall can't block/see what's going on. SonicWall Netextender is 11 ranked solution in top Enterprise Infrastructure VPN tools.

Sonicwall netextender routing issues