1

We are utilizing (or, I should say, trying to utilize) the SonicWall Mobile Connect app with Windows 10 to establish SSL-VPN connections.

It appears that either Windows or the App has changed how it handles credentials. We are no longer being prompted to enter a domain\username and password when we establish a connection. It just tries to connect using the logged in user’s credentials. This is ok as long as the person is using a domain joined machine. But if someone is using a non-domain machine, then obviously that person’s local or home username is not allowed… and so the connection fails. It never prompts to change or enter that info.

Event logs are showing this to be the case.

Additional information:

  • This is a recent event. It didn’t use to work this way. Something has changed recently with either Windows or the App.
  • It is happening on all new Win10 setups.
  • Users who were previously setup, before this issue popped up, are fine. It is like their credentials are cached.
  • The SonicWall Mobile Connect App does not allow you to enter in credentials during setup. Those fields are grayed out and unusable. This is typical and how it has always worked, however, usually it will prompt you to enter those credentials upon first connection attempt. That no longer happens. It just tries to use the local login credentials and then fails.
3 Spice ups
2

What firmware version are you using and what version of Win 10 is it?

Have you tried using the windows netextender client instead of the mobile client?

3

Have you checked Credentials Manager in Control Panel? Perhaps you can deleted the saved username/password there.

4

Latest firmware (although this is not a firewall issue, this appears to be a windows and/or sonicwall app issue) and latest version of windows.

Netextender is no longer supported on Win10, so we try not to use it. But if we can’t get this to work soon, we’ll have to give it a shot.

5

Yeah, there is nothing in there, which sort of makes sense since the app is not actually asking for any credentials. It is just using the logged in user’s windows credentials.

6

May be somebody from spiceworks can assist on this issue?

7

True, but it was the only route we could take too.

I’ve had to role out Netextender on 16 clients mate as everything else was proving too painful. Other than the odd unusual issue (losing settings or service stops) it works as intended (even on 1703)

8

Update:

I reached out to SonicWall support and was told to stop using the Mobile Connect App with Win10. They told us (I’m closely paraphrasing) “That app was originally developed for Mac, we started using it for Windows 10 when NetExtender was having problems, but we’ve since run into problems with the App and the Creators Update so we’re now asking people to use an updated version of NetExtender.”

I’ve tested this “updated version of NetExtender” and it did indeed work, without the previous problems we ran into with Netextender and Win10.

HOWEVER, the version is 8.6.263, which is NOT the version that is offered on MySonicWall… so other than contacting support directly, I don’t know how you would get this.

1 Spice up
9

I spoke to Sonicwall support. They sent me that version and it works. I can share it from Google Drive. I’m not sure if I can post links on here or if someone wants to email I can send it them with rename the .exe.

10

Yes, it works for me also. I have downloaded the Client directly at the spiceworks Website.

You can find it in the demo section of the firewall device.

Many thanks for your Support!

Best Regards.

Marc

11

Could someone post a download link for th 8.6.263 NetExtender version?

This thing has been bugging me all day today and it seems that the .263 build is the only solution.

Thanks a lot in advance.

@jackiegibbs

12

Did you get the 8.6.263 version or you still need it?

13

I just took a look at the MySonicWall page, and it appears that they are now offering version 8.6.20 for download there. That is not the version support gave us specifically to use, but it is still a version that works with Windows 10. I tested it out and it seems ok. So, if you can’t get yoru hands on 8.6.263, grab the .20 from MySonicWall and give that a go.

By the way, some people are reporting problems with NetExtender after the Fall Creators Update. It looks like uninstalling, rebooting, reinstalling resolves those issues.

14

Can I post a Google drive link on here? I have it shared but don’t want to break any rules.

15

Hi,

I do still need it, could you please share it with me?

Kind regards
Werner

@susrutabhat

16

Here is the link. Hopefully it shows up. Let me know if it doesn’t.

https://drive.google.com/file/d/0B78M53Orcc9Dc2RQWjV4THZHVGs/view?usp=sharing

17

@jackiegibbs

Thanks alot.
I was able to download the file and it worked right away in Win10 / build 1703.

@jackiegibbs

18

Thanks for the download link, worked great.

Have access to MySonicwall but still updated version is not there, and this was quicker than doing a support ticket :wink:

Also, for reference/searching - https://www.sonicwall.com/en-us/support/knowledge-base/170707194358278

Damaged Version of Net Extender Error Message on Windows 10

@jackiegibbs