I have a user’s laptop which is one of the new Surface Pro Laptops with the Snapdragon ARM processor. I assume because of this processor i can’t get net extender to work as I keep getting drivers errors with the sfpmonitor.sys not loading in event viewer after trying to uninstall and reinstall multiple times. I saw in another sonicwall post on sonicwall forums saying it not supported.
So after seeing this, I tried using Mobile Connect. It would connect maybe 1 out of 10 tries if I keep trying. Everytime i try connecting, it gives me a warning about “failed to read socket” almost everytime it fails instantly. Not sure what causing mobile connect not to work but event viewer shows error code 2500 for this mobile connect problem.
Any help with this?
I know the connection works if I try it on another machine so it not a user/pw or setup incorrectly problem for the SSLVPN.
I did try using a slightly older net extender and the newest from the mysonicwall dashboard. Version 10.2.331 and 10.2.339 and 10.2.340
Net extender keeps giving me either intiializing engine…failed or initizaling parameters…failed errors.
I have found the Mobile connect client to be really reliable personally.
The one failure mode I have seen was fixed by uninstalling the client, rebooting, and reinstalling and setting up a new profile.
Are you using an IP or FQDN to target the SonicWall?
Is there any update? I’m experiencing the same issue with the same symptoms. I have a new Surface Pro 11, and since it has an ARM processor, I can’t use it remotely because the VPN with a NSA 3700 doesn’t work.
I have this issue with a new Surface Laptop 7 with ARM. I think it has to do with the system going into sleep without disconnecting. Restarting the system seems to resolve it but if connected, close the lid and come back later it is not connected and I get the Failed to read socket error.
We ordered a replacement laptop with intel processor (they still do have them but you need a business account to get it). It shows on their site that you can’t use ARM processor with sonicwall (sonicwall website). Only other option is use Mobile Connect which for us didn’t work.
Is it wonky because it is an IP not a hostname? We use a real SSL cert for ours it made things a LOT better. The device not working wouldn’t be behind anything that would block port 1234 I don’t suppose?
I found that if I go to the Sonicwall Mobile Connect app, next to VPN turn on the connections, it takes me to the windows VPN, I then connect there and it works.
The difference from what I was doing is I was not going to the mobile connect app first. On my intel based machine I can just go to the windows VPN and log in from there. I need to continue to use to see if I still have a connection error or if this will work even after sleep.
Have used IPs reliably in the past. The hostname is nice for a slue of other reasons.
I don’t think they are using 1234 as the port, just as an example.
Unlikely that they would be blocking port 443, which is the default.
But possible if they are using a non-standard port it could be getting blocked, though I would think it would be all the time, not intermittent.
Agree. I reread it and I’m thinking that virtual nic driver isn’t working with ARM it’s likely only x86. We moved off 443 to avoid all the ssl scan attacks and the port we picked did have some issues with a few people