Netextender Windows 7 Failed Install

Posted on by

I have been playing around with Windows 8 and found that the version of netextender that I have installed will not work with Windows 8. Problem is that when you go to install a newer version it requires that you uninstall the old version first. That is easier said than done sometimes since it appears that you have to be logged in as the user that installed netextender in order to be able to uninstall it.

Netextender Windows 7 Failed InstallSonicwall Net Extender Windows 7

(Some hacker at Sonicwall is having a good chuckle over that one). This PC was upgraded from a windows 7 image and the user profile that originally installed sonicwall has long been deleted. So I am unable to log in as that user. Also, the option to have netextender automatically uninstall itself after use has been greyed out. Does anyone know another way to uninstall so that I can upgrade to a newer version?

Thanks in advance, Zack Godwin. Terry_kantorowski2 wrote: There is an uninst.exe file in the program files directory of older versions (3.5.xxx and earlier). If you copy and run from the program files directory of the computer you want to uninstall, you can remove with any logged in user. Hopefully, Sonicwall will make this process easier now that Dell has acquired them. Werewolf Wild West Companion Pdf Printer.

We had version 4 installed. Seems like only the Windows 7 computers had this issue of not showing up in the uninstall list. Was able to download 3.5 and get the uninstall.exe.

Ran it from the install location and that allowed us to update NetExtender to 6.0. Saved us beaucoup time considering all the computers this was happening on.

I am running a Sonicwall NSA 3500 on SonicOS Enhanced 5.9.1.5 16o. On several laptops we use NetExtender Windows Client Ver. 7.5.223 running on Widows 7 x64. These are all Dell Precision workstations. We use a combination of Sonicwall Global VPN and NetExtendar SSL-VPN. A lot of us prefer NetExtender because of it's performance and stability which had been great for the last couple of years. After the last Windows update in June, NetExtender came to a screeching halt.

Sec is scheduled to support Windows 7 in 2. Bit)While installing, qsfilter. Bit)Fails to install. Not Windows 7specific issue. Wall Global VPN Client. Get an error: Failed to open the IPSec driver. Not a regression. Users can uninstall and reinstall after upgrade. Clean installation on Windows 7 works fine.

Looking at the logs this is the message: Status ID: 0x06000308 Source: Engine Description: NetExtender has been disconnected for one of the following reasons: -There was a break in the network connection -The connection was idle for longer than the configured idle timeout -Your user account was logged out of the SSL VPN portal Then the second message.... Status ID: 0x0000314 Source: Engine Description: Remote Access Service error!

(Rebooting might resolve the problem) Attached data: RAS Error 651: The modem (or other connecting device) has reported an error. Of course I rebooted and got the same messages. The day this happend I rolled back Windows to a time before the update. NetExtender worked again.

Then a week later I was prompted to allow the Windows update to happen again. Then I though I could troubleshoot the NetExtender issue by checking for updates and installing those that were needed. Still no luck. I checked the timeout settings on the Sonicwall, no luck. I extended the timeout settings, no luck. NetExtender also fails on one other user's Precision after she allowed the update to occur. Has this happened to anyone else?

Any Ideas on where to go from here? Internet Explorer 8.0 Version For Windows 8 on this page. What's inside the last Windows Update that would break SSL-VPN? Oh, I also run SonicWall SSL-VPN App.

That works without any issues. So the issue cannot be on the Sonicwall. This may be chasing ghosts (and I haven't had TOO much admin exposure to NetEx) however I know after the most recent set of Windows updates, which were applied to our servers, we had some issues with our remote locations accessing network locations over the WAN using SMB. This is a totally different protocol from VPN, but the fundamentals are there. The issue was discovered that Microsoft has decided to tighten some security features on NetBIOS and the way that is communicates. If there is a proxy involved, well.