SonicWall Mobile Connect 应用的评论

SonicWall Mobile Connect Macs 应用的评论 Apple Mac App Store

45

Does the job, but not internationally

Connecting within the US it seems to do its job well. But it fails to establish a proper connection from extremely remote destinations.

Closing the window confuses novice users

Annoying bug: if you close the connection window, and later want to bring it back up but haven’t fully quit the app, you need to go to the Window menu and click Bring All to Front. If the main window is closed, and someone clicks on the Dock icon to bring it back up, it should automatically re-open the window. Confusing 10+ novice users in a small office, I’m getting phone calls daily because of this.

Can’t add a connection

Running version 4.0.3 on OS X 10.10.5 I can’t add a connection. Useless as is.

Broken

It used to work with secondary authentication, that no longer works. It states that it doesn’t work with iOS so it is clearly confused. We are probably going to start scrapping all out client SonicWALLs anyway since their support has gone down-hill in the past couple of years.

Does not work on OS X El Capitan

It worked great on OS X yosemite but after I upgraded to El Capitan, it stopped working. I am not able to connect to my VPN for work. It connects and immediately disconnects.

Terribly Slow

Introduces hundreds of miliseconds of latency vs alternative VPN connection product, making it almost useless. In this case when used on Mac OS 10.11.3 . With SonicWall Mobile Connect: 64 bytes from X.Y.Z.1: icmp_seq=0 ttl=64 time=1115.139 ms 64 bytes from X.Y.Z.1: icmp_seq=1 ttl=64 time=714.865 ms 64 bytes from X.Y.Z.1: icmp_seq=2 ttl=64 time=1039.439 ms 64 bytes from X.Y.Z.1: icmp_seq=3 ttl=64 time=1273.709 ms With competing VPN client product: 64 bytes from X.Y.Z.1:: icmp_seq=37 ttl=64 time=305.875 ms 64 bytes from X.Y.Z.1:: icmp_seq=38 ttl=64 time=305.697 ms 64 bytes from X.Y.Z.1:: icmp_seq=39 ttl=64 time=307.430 ms 64 bytes from X.Y.Z.1:: icmp_seq=40 ttl=64 time=307.513 ms It’s fascinating how bad SonicWall client software stays year after year for the Mac environment.

Reboot madness

If you forget to shut this guy off below heading in the office beware! It jsut spools and spools until it has eaten all your RAM and starts in on your hard drive. Not only do you have to force quit the app but also the service NEAGENT. I was left with a machine that believed it only had 1 gb of space left when it really had 100. It amazes me that a bug like this can make it into the wild and for so long! It has been this way for almost a year now. Outside of that it works pretty well away from the office. I would say it connects but isn’t really connected about 25% of the time on the first attempt but disconnecting and reconnecting clears it up and from there the connection rarely drops even of the worst of hotel wifi. If not for that crazy bug I could easily give it 4/5.

How the heck does it work?

Add connection - No connection. No instructions. Does a user have to be drunk to make this work?

Ottima , funziona su 10.11.2

Consiglio vivamente.

Works!

In OSX 10.11.2 Netextender stopped working (again) so I had to find some alternative and this is basically the same thing but it atually works.

Poorly Written Code

If disconnected from a good VPN connection then connected behind the Firewall, while still runnin the application will peg the CPU a 100% causing the need to reboot. Force quitting does not do it. Other than that it works great.

Filled my hard drive up with error logs - literally

Like another reviewer mentioned, there is a serious flaw in this app, at least on El Capitan. Works great at first, but after disconnecting, the app will silently start consuming massive amounts of CPU and hard drive space (over 60 GB!!!) generating a torrent of error logs. It filled my hard drive and almost crashed my system before I could figure out what was going on, kill the process and clear out the log folder. Watch out!!

Adds a default route on El Capitan

Haven’t had this before - 3.1.6 adds a default route (alongside my normal default route) !! Normal VPN connections in OSX have the option to “send all traffic through connection” but this one doesn’t. Please fix this!

freezes MacBookPro with 100% cpu usage

When I move between networks (for instance when I go from office to home) , sonicwall mobile connect freezes my MacBookPro 11,3 OSX 10.11. it keeps burning CPU usage on 100% and doesn’t repond and I have to force quit it.

Works with El Cap after NetExtender Crashes

After upgrading to El Capitan, netextender stopped working. After troubleshooting it briefly a forum mentioned that still Mac Store App worked. Lo and be hold it did and got us running again after upgrades. We even have 2-factor authentication. I haven’t used it long enough to test if it crashes much, but jsut being able to connect is nice.

Sprawny i szybki SSL VPN

Bardzo prosta, ale działająca szybko i sprawnie aplikacja. Integruje się z Preferencjami systemowymi Sieci w OS X. Polecam.

Thrashes your CPU if it can’t connect

When it works it seems to work fine. However, one key annoyance is whenever I return to my office having used Sonicwall to VPN in from home, the process just thrashes the CPU trying to reconnect (which it can’t from our corporate network due to how our routing rules are setup). You can kill the Sonicwall app but your CPU continues to thrash (and thereby demolishing your battery life). What you need to do is go into Activity Monitor and kill the “neagent” process. Then you’ll get your CPU and fan back. Please fix this.

Works Just Fine - Don’t let the bad ratings scare you!

This client works great, but you do have to set things up porperly. I had to go through a little learning curve, but got it to work fine. First of all, your SonicWall needs to have the latest formware, or at very least something within the last year or so. This is key. You cant expect a current version of a sensitive application like a VPN client to run with old firmware on the firewall? It goes against safe VPN concepts. * I had the issue with the client not disconnecting and had to reboot my older Mac, but once I updated formware on the firewall and configured the firewall porperly, the permanent disconnting error went a way. The other thing to know is that it uses “Search Domains” for DNS on the firewall side. Without proper configuration on the firewal side, nothing will resolve correctly over the VPN tunnel. This is by design. It works perfectly once you set up proper searches. The “How To” docs are ok, but not that easy to find unless you really know what to hunt for. I admit, I lamost gave up. But once I found what I was looking for, I got it configured pretty quickly and am now convinced it’s fairly decent VPN client!

Half the speed of NetExtender in a Windows 10 VM

After having my staff create support tickets regarding the speed of NetExtender on OS X, I started seeking a solution- auditing bandwidth management and firewall rules on my NSA 3500, tweaking the cipher suites, ect, and the speed to bring data from the office to a remote user over SonicWall Mobile connect was always disappointing. Then I had a “what if?” and installed NetExtender client in a Windows 10 VM on the same Mac. Speedtests run through the VM/NetExtender are twice as fast as done natively through SWMC on OS X. Even old Java-needing NetExtender on OS X is faster than the shiny new App Store app. Bottom line: slow app is slow. It works, but have patience if you have to transfer files. You’re gonna be frustrated. Which basically summarizes everything around SonicWall products and MacOS.

It’s rare to have to reboot your Mac… but this app may require it very often

When it works it is great, but then once every few days it freezes, requiring Force to Quit. At that point any time you try again to start it it will freeze again until your Mac reboots :( Not what you expect from a professionally developed application, especially one you depend on for day to day work.

  • send link to app