My NetExtender VPN will no longer connect with the Lion upgrade. Can anyone help me?

I'm running into problems too! I just upgraded to Lion yesterday and my Net Extender (4.0.667 – it’s the version IT is supplying) is returning this error message:

FATAL: You don’t have permission to read/execute‘/etc/ppp/peers’.

I've been trying to modify permissions on this folder but my system can't find it!

Here are other tips I've received or found and tried with no luck - using Terminal, I've entered:

sudo chmod u+s /etc/ppp/peers

No luck... also,

sudo chmod -R 777 /usr/sbin/pppd

No luck so far...

Have you tried this?

http://www.macwindows.com/snowleopardVPN.html#102510a

1. Go directly to: https://sslvpn.demo.sonicwall.com/cgi-bin/portal#
2. Click on the NetExtender button(which opens this link: https://sslvpn.demo.sonicwall.com/cgi-bin/portal#)
3. Follow the instructions andpermanently APPROVE the SonicWALL permissions dialogs that pop up.

@ernopena_nyc: Thank you!!! Fixed solved my problem with Sonic Wall netExtender on Lion.

I have not found this to be a solution in my case. I have some Apple OS users, Fedora/Ubuntu users and Windows 7 users who are using the SonicWall client. They can connect to either location in the US fine. Once connected, they receive a DNS search domain of pppFrameEncoded =0; instead of our AD domains which are passed fine in Windows and additionally the correct DNS servers (IP addresses) are listed in preference above the local router IP of the user.

I found that the correct DNS and routes were listed in the SonicWall client and while could ping the IP of the resource, I could not resolve its hostname with the Network Utility. After manually adding the Search Domains (we have two) in preference and removing the previous above, I was then able to resolve lookups to the FQDN and IP but not the hostname. This really ***** for our Apple users who are mainly execs and use samba connections to shared resources. Strangely enough this also seems to impact the Apple iPad and iPhone 4 I have on iOS 5.1 as well. Any thoughts anyone? Can connect with no error, ping IP, can resolve easily FQDN and can access resources by IP or FQDN but not by hostname.

172.xxx.xxx.xxx works fine

smb://hostname.sub.domain.com works fine

smb://hostname does not but resolves

Anyone else run into this? It doesn't affect any Windows users at all.

Thanks, fixes the issue for Mountain Lion as well. Company IT provided Version 6, needed Version 7 to actually get into the file share.