cancel
Showing results for 
Search instead for 
Did you mean: 

Pulse Secure Client 9.0.4 in MAC OS Mojave Crashes while trying to connect to Juniper SRX345

Highlighted
New Contributor

Pulse Secure Client 9.0.4 in MAC OS Mojave Crashes while trying to connect to Juniper SRX345

We are finding issues with connecting Juniper SRX345 (firewall) using Pulse Secure 9.0.4 Client in MAC Mojave(10.14.6).

Our engineering LAB VPN is setup using Juniper SRX firewall and we connect this using Pulse Secure Client. But when we use MAC Book (Mojave) with Pulse Secure 9.0.4 client it is crashing continuously and we are unable to connect to the LAB VPN.

I have contacted the Juniper support and according to them they will support to only till 'Pulse Secure' 5.1 version. For anything above 5.1, we need to contact Pulse Secure as they manage this client now.
This problem is only with MAC Pulse Secure 9.0.4 version. Same version Windows Pulse Secure client we are able to connect with Juniper SRX and there is no issue!

Pulse secure version:- 9.0.4
Juniper SRX345(Firewall)
Junos :- 15.1X49-D150-2
MAC OS Mojave :- 10.14.6

Crash Report 

------------------

Process: dsAccessService [6096]
Path: /Applications/Pulse Secure.app/Contents/Plugins/JUNS/dsAccessService
Identifier: dsAccessService
Version: ???
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: dsAccessService [6096]
User ID: 0

Date/Time: 2019-09-05 15:04:11.052 +0530
OS Version: Mac OS X 10.14.6 (18G95)
Report Version: 12
Anonymous UUID: 07ECE63E-E292-6529-CF29-A820E72D438F


Time Awake Since Boot: 7200 seconds

System Integrity Protection: enabled

Crashed Thread: 19

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xffffffff00000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [6096]

VM Regions Near 0xffffffff00000000:
--> shared memory 00007fffffe1d000-00007fffffe1e000 [ 4K] r-x/r-x SM=SHM

Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff65a7722a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff65a7776c mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff399ee1ee __CFRunLoopServiceMachPort + 328
3 com.apple.CoreFoundation 0x00007fff399ed75c __CFRunLoopRun + 1612
4 com.apple.CoreFoundation 0x00007fff399ecebe CFRunLoopRunSpecific + 455
5 com.apple.Foundation 0x00007fff3bc5132f -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 280
6 dsAccessService 0x00000001079bd8cc DSAccessServiceVendor::Vend(unsigned int) + 300
7 dsAccessService 0x00000001079bcb90 CmdRunService() + 100
8 dsAccessService 0x00000001079bc5ee main + 419
9 dsAccessService 0x00000001079bc2e4 start + 52

 

 

4 REPLIES 4
Highlighted
New Contributor

Re: Pulse Secure Client 9.0.4 in MAC OS Mojave Crashes while trying to connect to Juniper SRX345

Any help?

Occasional Visitor

Re: Pulse Secure Client 9.0.4 in MAC OS Mojave Crashes while trying to connect to Juniper SRX345

Any updates here?  I am experiancing the same issue (same Mac OS version) with Pulse Secure 9.1.3 (1413).

 

Highlighted
Community Manager

Re: Pulse Secure Client 9.0.4 in MAC OS Mojave Crashes while trying to connect to Juniper SRX345

Hello All,

 

We work very closely with Juniper Networks on compatibility with SRX.  Please contact Juniper Networks to open a ticket to obtain the proper software version for the Pulse Desktop Client.

Highlighted

Re: Pulse Secure Client 9.0.4 in MAC OS Mojave Crashes while trying to connect to Juniper SRX345

Same problem here, when I use Pulse secure 9.1 on windows, all works fine, but when use same pulse secure client on MACosX Catalina, get a infinite loop after authentication.

 

I dont believe it is a Juniper problem.

 

00126,09 2020/03/18 19:51:00.744 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1692 - 'TM' ipsec remoteAddr=172.31.0.0

00129,09 2020/03/18 19:51:00.744 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1693 - 'TM' ipsec remoteMask=255.255.255.0

00112,09 2020/03/18 19:51:00.744 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1694 - 'TM' ike dhGroup=2

00109,09 2020/03/18 19:51:00.744 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1695 - 'TM' ike auth=2

00115,09 2020/03/18 19:51:00.744 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1696 - 'TM' ike encr=8388620

00118,09 2020/03/18 19:51:00.744 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1697 - 'TM' rekeyIpsecSaCount=0

00117,09 2020/03/18 19:51:00.744 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1698 - 'TM' rekeySeconds=28800

00114,09 2020/03/18 19:51:00.745 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1699 - 'TM' ipsec natmode=2

00115,09 2020/03/18 19:51:00.745 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1700 - 'TM' ipsec pfsGroup=2

00111,09 2020/03/18 19:51:00.745 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1701 - 'TM' ipsec auth=2

00117,09 2020/03/18 19:51:00.745 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1702 - 'TM' ipsec encr=8388620

00118,09 2020/03/18 19:51:00.745 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1703 - 'TM' ipsec idleTimeout=0

00124,09 2020/03/18 19:51:00.745 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1704 - 'TM' ipsec rekeyKOctets=500000

00122,09 2020/03/18 19:51:00.745 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1705 - 'TM' ipsec rekeySeconds=3600

00121,09 2020/03/18 19:51:00.745 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1706 - 'TM' ipsec sessionTimeout=0

00118,09 2020/03/18 19:51:00.745 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1707 - 'TM' persistent tunnel=1

00130,09 2020/03/18 19:51:00.745 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1712 - 'TM' clientVendorID=JNPR IPSec Clien

00110,09 2020/03/18 19:51:00.745 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1714 - 'TM' clientID=33

00167,09 2020/03/18 19:51:00.746 3 root dsAccessService dsTMService p51368 tBB23 platform.cpp:194 - 'RM' Data route: 0.0.0.0/0 -> 172.20.10.1 (metric:0) (if_id:4) (hw_addrSmiley Happy

 

00167,09 2020/03/18 19:51:00.746 3 root dsAccessService dsTMService p51368 tBB23 platform.cpp:194 - 'RM' Data route: 127.0.0.0/8 -> 127.0.0.1 (metric:0) (if_id:1) (hw_addrSmiley Happy

 

00168,09 2020/03/18 19:51:00.746 3 root dsAccessService dsTMService p51368 tBB23 platform.cpp:194 - 'RM' Data route: 127.0.0.1/32 -> 127.0.0.1 (metric:0) (if_id:1) (hw_addrSmiley Happy

 

00168,09 2020/03/18 19:51:00.746 3 root dsAccessService dsTMService p51368 tBB23 platform.cpp:194 - 'RM' Data route: 169.254.0.0/16 -> 0.0.0.0 (metric:0) (if_id:4) (hw_addrSmiley Happy

 

00168,09 2020/03/18 19:51:00.746 3 root dsAccessService dsTMService p51368 tBB23 platform.cpp:194 - 'RM' Data route: 172.20.10.0/28 -> 0.0.0.0 (metric:0) (if_id:4) (hw_addrSmiley Happy

 

00168,09 2020/03/18 19:51:00.746 3 root dsAccessService dsTMService p51368 tBB23 platform.cpp:194 - 'RM' Data route: 172.20.10.1/32 -> 0.0.0.0 (metric:0) (if_id:4) (hw_addrSmiley Happy

 

00168,09 2020/03/18 19:51:00.746 3 root dsAccessService dsTMService p51368 tBB23 platform.cpp:194 - 'RM' Data route: 172.20.10.3/32 -> 0.0.0.0 (metric:0) (if_id:4) (hw_addrSmiley Happy

 

00146,09 2020/03/18 19:51:00.746 3 root dsAccessService dsTMService p51368 tB03 addpolicy.cpp:1665 - 'TM' AddPolicy(p_189.4.4.182_2_7f8ff9004cf0) success

00165,09 2020/03/18 19:51:00.746 3 root dsAccessService dsTMService p51368 tBB23 platform.cpp:194 - 'RM' Data route: 224.0.0.0/4 -> 0.0.0.0 (metric:0) (if_id:4) (hw_addrSmiley Happy