Sonicwall NetExtender and Snow Leopard

Seems like pppd is no longer setuid anymore. To correct this, fire up terminal and enter the following:

1
sudo chmod u+s /usr/sbin/pppd

This will enable NetExtender to once again work its magic.

7 thoughts on “Sonicwall NetExtender and Snow Leopard

  1. I don’t understand your instructions. But, I need help too. I have been using net extender for a year without any problems. I installed Snow Leopard two days ago and haven’t been able to get it to work since.

  2. Wood, I recently upgraded the software running on our SSL-VPN and that pushed version 3.5.636 of NetExtender. Make sure you are running that version. I am not having any issues with this version.

  3. I entered:
    sudo chmod u+s /usr/sbin/pppd

    the message below came up…
    is it wise to proceed??

    WARNING: Improper use of the sudo command could lead to data loss
    or the deletion of important system files. Please double-check your
    typing when using sudo. Type “man sudo” for more information.

    To proceed, enter your password, or type Ctrl-C to abort.

    Password:

  4. I have figured out how to get around issues where you lose DNS and you have netextender installed. I have found that if you add the IP and hostname of your VPN to your host file, then you open your netextender, connect to your VPN then disconnect. This will then reset your DNS to work properly. I have a feeling that netextender does some stuff to your DNS and that if netextender is not exited gracefully (i.e. crashes) then it cannot clean up the mess it made to your DNS. So if you can get it to connect and then disconnect gracefully, it will clean up it’s own mess.

  5. @A K, thank you! You gave me an idea of how to fix my issue. I found that if my netextender doesn’t shut down properly then it kills my os x dns and I can’t surf the net or get email etc. I found that tethering with my iphone also messed up netextender, at least when I disconnected from tethering. I also had the problem arise after a (rare) kernel panic error. This time it was a quick fix, I went to my Network Utility, I went to the Lookup tab, pasted in the domain that is set in my netextender, got its IP, then connected to vpn using the IP instead of domain. That works. Then disconnecting from netextender also works, after which everything about my dns is back to normal. Again, thanks!

Leave a Reply

Your email address will not be published. Required fields are marked *

*


*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="" highlight="">