11/8/2022 0 Comments Dell aventail vpn client![]() ![]() 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |