Hey IT friends

My company uses NetExtender with SonicWall sslvpn licenses to give users outside access to our file shares and intranet sites. When it works, it does it’s job well. However, we tend to have more issues than not. If a user mistypes their password, the program just says “verifying user” forever. And by forever, I timed it once to over 10 minutes before I gave up. The only way to fix it is to close out, then go and reboot the service, then try again. Then people have random issues where it doesn’t want to work at all, and we have to reinstall multiple times, or use different versions to get it to work. The most common of those errors is “initializing engine failed”. We are all using Windows 10. Currently we are on 1809, but we have had these issues for years. All laptops also use different versions of the NetExtender client.

Am I the only one? Has anyone moved away from NetExtender and found a reliable SSLVPN client that works with SonicWall?

4 Spice ups

Sounds like we are pretty much in the same boat as you, although we do not have the same issues as you. I can confirm that I too have seen the password thing and yes I have had to restart the service on the PC.

1 Spice up

Since you have Windows 10, switch from NetExtender to the MobileConnect app (if you can’t switch to that GlobalVPN licenses and use that client instead). I have found that once NetExtender decides it’s not going to work, you’re toast.
Also, be sure to check your SonicWALL events, filtered by SSLVPN (enable them in Log | Settings if they’re not already). You might be able to see which phase things are failing so you can get support.

1 Spice up

Is your SSLVPN integrated with LDAP?

1 Spice up

No we create the users on the SonicWALL.

What version of NetExtender are your users using? The old versions definitely have some problems on Windows 10, but they have fixed much of this in the newer releases.

1 Spice up

I would recommend against this. I frequently find the mobile connect app does not properly prioritize the DNS settings of its connection over the local network’s DNS setting, so you’ll find you’re unable to reach servers by DNS names.

1 Spice up

Correct, that is one of the issues with Mobile Connect. DNS does not work as needed. Also if you change the WAN location of your Sonicwall or SMA unit then you will need to remove the Mobile Connect profile, reboot and then set it up again.

2 Spice ups

I’ve run into that exact problem and SonicWALL support was, well, clueless. The Mobile Connect App is light years above the old Netextender, but this is the one issue with it in Windows 10.

As to Linux, NetExtender has an issue where in Fedora Core, you have to reset your /etc/resolv.conf file when it disconnects. Pain in the … But kind of a similar “DNS gets messed up” issue just like Windows 10 Mobile Connect.

1 Spice up

@tbinct ​ We use versions from 8.x.x to the current 9.x.x. It actually seems that the 8.x.x are the least of the problematic ones.

I didn’t even notice there was a 9. I’ve been using the later 8.6.x revisions.