So, add the necessary rules, both on the INSIDE and DMZ interfaces to allow traffic to and from your LAN to and from the netextender client IP subnet. SW TZ-105 - Unable to resolve local DNS when connecting to office network using Sonicwall VPN Mobile Connect or NetExtender The offices network is peer to peer so there is no on site DC nor a DNS server so of course the Sonicwall itself handles all the IP, DHCP and DNS duties. You still have to allow that netextender client subnet access to your LAN in your PIX rules. If your LAN's default gateway is a core switch inside of your LAN, add a route there to send the traffic for the netextender's subnet to the PIX inside interface, then also add the route in the PIX to route it to the SSL VPN appliance in the DMZ. I have disabled the Advanced Security, but this did not help with problem.
![sonicwall netextender not connecting sonicwall netextender not connecting](https://bloginformatique178185015.files.wordpress.com/2019/01/sonicwall.png)
If I connect to the free Xfinity wifi it works without a hitch, but it does not connect with my personal wifi. It was working fine until yesterday morning. I am having issues connecting to my work Sonicwall NetExtender VPN. So, if your LAN's default gateway is your PIX, you'll just have to add a route in your PIX for the 192.168.20.0/24 subnet with a gateway IP of your SSL VPN appliance (.x in your DMZ). New issue connecting to SonicWall NetExtender VPN.
#Sonicwall netextender not connecting how to
Now, you have to tell your PIX and your LAN how to get to that netextender client range (192.168.20.0 in this case). Now, you want to configure your netextender IP range as something OFF your LAN, probably another .x/24 subnet that's different than your DMZ subnet, and I'd recommend making it something high, like 192.168.20.0/24 as to prevent interference for home users that are using default LAN IP subnets like 192.168.1.0's and 192.168.0.0's.
![sonicwall netextender not connecting sonicwall netextender not connecting](https://i.ytimg.com/vi/F91neNAPhMA/maxresdefault.jpg)
Delete the following path: C:\Program Files (x86)\SonicWall\SSL-VPN\NetExtender. So, it sounds like you've assigned the Sonicwall a DMZ IP of .x and you're NAT-ing your SSL traffic to it from a public IP for the virtual office connection. Run the NetExtender cleaner tool as Administrator.
#Sonicwall netextender not connecting pro
It sounds like you're on the right track. My employer uses SonicWall NetExtender to allow us to tunnel into a private network for file server access and RDP access office PC's all has been working fine until I recently installed Bit Defender Total Security 2013 on my Windows 8 Pro 64bit Dell laptop (XPS 15) and now NetExtender refuses to connect to the VPN server and does not invoke any port alerts from BitDefender to allow or block.