SLog64.dll (by SonicWALL) - SonicWALL SLog DLLĭell SonicWALL NetExtender program security rating.NECore.dll - NetExtender Core (SonicWALL NetExtender Core DLL) When using the SonicWall SSL VPN with Windows 10, if you are having issues with Mobile Connect or would just prefer your clients to use NetExtender.NxRas.dll - NetExtender CustomDialer (NetExtender CustomDialer for RAS).NEService.exe - NetExtender Windows NT Service (SonicWALL NetExtender Windows NT Service).NEUpdUI.exe - SonicWALL NetExtender Updater UI.
An i386-compatible Linux distribution is required, along with Sun Java 1.6.010+. There are a few version of the Sonicwall NetExtender, the version I m dealing with is 4.0.138.
Sonicwall Netextender 8.6 driver digital signature. The result was a DNS issue when tabbing between the RDP connection and the Windows 10 desktop. The problem I had was that Windows 10 tried to automatically use connections and DNS from all adapters. (I did not know that they needed to be rebooted) Assuming this resolved the problem I'll start rebooting the SMA once per quarter. I have had issues with Windows 10 and NetExtender (never an issue with Windows 7). I believe that the appliance had been powered on without being rebooted since we deployed it about two years ago. I've tested on 4 users, all are now able to connect via NetExtender with no issues. I rebooted the SMA and my users are once again able to connect. Anyone else having this problem? Any ideas? If you cannot see the process below, click here to see what to do when you get the damaged version of NetExtender. I can't tie this to a windows or office update. It is a Driver signing verification in Windows 10 that causes version 8.6 of NetExtender to show as Damaged, so when Windows does not let it pass the HCK (Windows Hardware Certification Kit) testing. Users who I've been able to restore access break again within 3 hours. I've tried the work around linked below with limited success. For some reason, slowley, all of my NetExtender users are losing access to our network.