cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to connect macOS to juniper srx100

Highlighted
Occasional Visitor

Unable to connect macOS to juniper srx100

I have a client running MAC OS Catalina with Pulse Secure MAC v9.1r4.2-b1955 connecting to a Juniper SRX100. The client installs OK on the MAC and added remote site but simply cycles the connecting process and never connects.

 

Windows clients work without issue. Not seeing any errors on Juniper but we are seeing the inital connection attempt. Not a license issue as they can have up to 10.

 

Is there something I need to open on the MAC OS side or possibly on the Juniper besides HTTPS and IKE protocols.

 

Could something on the MAC be blocking the Pulse client from connecting.

 

Cheers,

Scott Murphy

5 REPLIES 5
Highlighted
New Member

Re: Unable to connect macOS to juniper srx100

I am having the same issue!  Windows 10 works, Mac doesnt.

Highlighted
Moderator

Re: Unable to connect macOS to juniper srx100

Please provide the Pulse Client logs and I will try to see the cause for the connection loop.

 

Pulse Client Logs:


1. Open Pulse Client.
2. File >> Logs >> Annotate >> "any-string"
3. File >> Logs >> Log level >> Detailed.
4. Replicate the issue.
5. File >> Logs >> Save as.

PCS Expert
Pulse Connect Secure Certified Expert
Highlighted
Community Manager

Re: Unable to connect macOS to juniper srx100

Are you able to raise a support case for this one? That way you do not need to post detailed log files on the public community space.

 

Update: removed detailed logs, with the agreement of smurphy.

 

Highlighted
Occasional Contributor

Re: Unable to connect macOS to juniper srx100

We have an old SRX Branch (650) running 12.3X48-D85.1 and Pulse client version 9.1.2 (1181) with both MacOS (multiple versions) and Windows 10. no issues with this setup. If you want to post your SRX config I can take a look. 

Highlighted
Moderator

Re: Unable to connect macOS to juniper srx100

Hi smurphy@nexicomgroup.net,

 

Client logs indicate that the Access Service of Pulse Client got crashed during the tunnel setup i.e. right after receiving the IKE parameters.

 

00119,09 2020/04/06 14:57:56.022 3 root dsAccessService dsTMService p99520 t7603 addpolicy.cpp:1707 - 'TM' persistent tunnel=1

00137,09 2020/04/09 09:31:58.391 3 root dsAccessService dsTMService p99807 tB207 mLog.cpp:324 - 'TM' persistent tunnel by a1pid=212881344,spid=0

 

00133,09 2020/04/06 14:58:02.103 3 root dsAccessService dsAccessService p99522 t307 service.mm:148 - 'AccessService' initializing service...
00182,09 2020/04/06 14:58:02.103 3 root dsAccessService dsAccessService p99522 t307 accessService.cpp:100 - 'AccessService' service did not shutdown gracefully, performing recovery tasks...

 

What does persistent tunnel means in-terms of SRX, is it similar to ESP only mode (no SSL fallback) which is available in Pulse Secure VPN? @TsUk6uh4oLfq2Z smurphy@nexicomgroup.net 

 

Thank you,

Ray.

PCS Expert
Pulse Connect Secure Certified Expert