Active2 years, 11 months ago
Apple remote desktop client. I have a problem trying to connect to a VPN using 'Juniper Network Connect'. It happened after I upgraded from Mac OS X Yosemite (10.10) to Mac OS X El Capitan (10.11).
It happened after I upgraded from Mac OS X Yosemite (10.10) to Mac OS X El Capitan (10.11). Ever since I upgraded to OS X El Capitan, though, Juniper Network Connect (VPN client) stopped working. First it just wouldn't launch. AT&T Global Network Client for VPN on Apple Mac™. 10.11 - (El Capitan) Important Install and Upgrade Steps. Do not move the AT&T Global Network Client folder to the trash. Use the AT&T Global Network Client Uninstaller app or allow the installer to upgrade the application. NetScaler Gateway Plug-in v3.1.4 for Mac OS X(El Capitan Support) Version 3.1.4 (357) onwards With the El Capitan release, Apple has made significant changes in the way applications are installed. We, at Citrix, have followed through on those changes and updated our plug-ins to work.
Ever since I upgraded to OS X El Capitan, though, Juniper Network Connect (VPN client) stopped working. First it just wouldn't launch. Mac os x remote desktop client for microsoft windows computers. I also upgraded to the latest Java version from Oracle. Now although Network Connect launches it hangs at the 'Establishing Secure Session' step. It seems as though the connection is established (since I lose internet access in this period) but it can't create a tunnel.
Before I had the same problem, and solved it using the solution provided here only making this:
But for 'El Capitan' it's not working.
Here are some lines of the log:
20151022170309.742528 Network Connect[p430.t2567] ncsvccontrol.error The service failed to configure the tunnel (ncsvccontrol.mm:262)
20151022170309.856101 Network Connect[p430.t2567] nc.mac.app.1202.error DSError 0x2cbc0fa0 domain=nc.mac.app code=1202 'ncproxyd failed to establish a tunnel, status = 4' 20151022170310.316057 Network Connect[p430.t76719] dsssl.error Cert hash is not SHA256. len=32 (DSSSLSock.cpp:1781)
Community♦
Wilson Alzate CalderónWilson Alzate Calderón
![Mac Mac](/uploads/1/3/3/9/133905634/419328270.jpg)
5 Answers
SergioSergio
We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.
As of July, it appears Juniper is still working on this. The conclusion of that thread claims you can get Pulse working again by:
- Downloading the Symantic Certificate Authority
- Rename
Symc_Cross_Root.txt
toSymc_Cross_Root.crt
- Open Keychain Access, select 'System' in the left pane
- Choose File>Import File.. And navigate to the file you just renamed
- If you see something about a VeriSign class 3 certificate you're doing the right thing. Click the drop down next to 'Trust'
- Select 'Always Trust'. If you get a little blue icon next to the cert, you should be good to go.
Please note I've not tried this myself. It's a hack to get around unpatched and misbehaving software. While I generally like Juniper, I don't use their software products and I don't trust their tech team as far as I can throw the SRX550 that once shit out on me during a server move. https://kgvlckt.weebly.com/mailbox-rebuild-for-groupwise-mac-client.html. This advice is coming to you from a stranger on the Internet, your mileage may vary, failure to fully test before upgrading in a production environment may cause herpes, etc. etc.
agentroadkillagentroadkill
Vpn Client For Mac Os X
I encountered the same issue, but managed to circumvent it using Pulse Secure. Which you may found the download link in the following page:https://www.ias.edu/ias_vpn_installers
FischchengFischcheng
![Vpn Client For Mac El Capitan Vpn Client For Mac El Capitan](/uploads/1/3/3/9/133905634/767170920.png)
Install Open Pulse Secure and add a connection by providing the url to sslvpn site. It will ask for credentials, provide as you do with network connect. You should be able to connect to vpn.
user1527651user1527651
As for me (Mac OSX 10.12 Sierra) it helps to reboot in the Recovery Mode and in the terminal execute following command: 'csrutil disable'. But this decision is very insecure!!!
ultraonultraon