Sonicwall netextender no internet access
- #Sonicwall netextender no internet access how to
- #Sonicwall netextender no internet access upgrade
- #Sonicwall netextender no internet access pro
Only the subnets/hosts you enter into the "Client Routes" section will be routed through the VPN.Īdditionally any DNS servers you enter into the the "Client Settings" will ALSO be routed through the VPN.
#Sonicwall netextender no internet access upgrade
all 5.9.x on SonicWALL NEVER release a GENEAL RELEASE!!! So, anyone using this, believe me, FULL backup your old firmware first, then Export your setting, maybe one day you need downgrade back to the GENERAL RELEASE version like me :-(Īny my downgrade also not happy, since just upload 5.8.1.5 and choose Boot it with current setting, it hang, I need go back to SAFE MODE, then using the last backup 5.8.1.5 (I click the backup button before I go upgrade to 5.9.1.1) to full restore it back, else I need many time to reset all setting (If you haven't export setting on hand).Ĭonsidering you have the "Tunnel ALL" option disabled (this settings enforces ALL traffic to traverse the VPN).
#Sonicwall netextender no internet access pro
Yes, I know 5.9.1.1 add many good function that we IT Pro like, but. So my final way is FULL downgrade back to 5.8.1.5, guess what? It work again as general.
#Sonicwall netextender no internet access how to
I used few hour try troubleshooting, try different setting, guess what? Yes, if I am let the Cilent DNS box empty, I using some network tools at IOS ping 8.8.8.8 it work, but without DNS, how to resolve Domain Name!? My Boss go outside work and using Mobile VPN with this told me can't access Internet anymore.
After I am upgrade to 5.9.1.1 later about two month. All Setting following SonicWALL Official KB.īefore using 5.8.1.5 it all thing work. : 192.168.1.150ĥ.9.x have many buggy, before I am using NSA 240, NSA 2400 with 5.9.1.1īut my SSL VPN is enabled Tunnel All Mode, since before I am also do this. I can't be the first person to run in to this problem - but I can't easily find the solution.ĭescription. I could reset some addresses - but in general, this problem seems impossible to avoid - in general, VPN users don't have control over the (internal) network addresses FROM which they connect - and no matter what you make the addresses, it seems as if there's a possibility of a conflict. At least this is what I think is happening. So when the guest is VPN'd in to the SonicWall, it's trying to send the traffic through its default gateway of 192.168.1.1 - BUT that traffic is resolving to the SonicWall and NOT the router on the guest network.
The remote (SonicWalls) LAN subnet is 192.168.1.0/24 and the SonicWall's internal address is 192.168.1.1 ALSO. I have a guest PC trying to VPN in to the remote SonicWall network using split tunneling.īoth networks have identical address spaces: What do people usually do to solve this issue? I suspect that the problem is related to address conflicts in the RFC 1918 space. Maybe what I wrote below is all wet - one of the SonicWalls to which I can connect successfully ALSO has the same address space.