Pulse Secure formerly SSL VPN
Showing results for 
Search instead for 
Do you mean 
Reply
Contributor
Posts: 44
Registered: ‎10-14-2010
0 Kudos

Re: Android Support

let me check right now, get back to you pretty soon.

 

Contributor
Posts: 44
Registered: ‎10-14-2010
0 Kudos

Re: Android Support

one is a SAMSUNG GALAXY SII and a S4 and a ASUS TABLET.

 

 

Contributor
Posts: 44
Registered: ‎10-14-2010
0 Kudos

Re: Android Support

0015, 09 2013/06/27 11:05:46 General Log sec net.juniper.junos.pulse.android Junos Pulse 7123 7123 User signed in.
00015, 09 2013/06/27 11:05:47 General Log sec net.juniper.junos.pulse.android Junos Pulse 7123 7123 User signed in.
00037, 09 2013/06/27 11:05:51 General Log sec net.juniper.junos.pulse.android Junos Pulse 7123 7123 Failed to download session parameters
00020, 09 2013/06/27 16:12:09 General Log sec net.juniper.junos.pulse.android Junos Pulse 2434 2434 User opened Connect.
00015, 09 2013/06/27 16:12:49 General Log sec net.juniper.junos.pulse.android Junos Pulse 2434 2434 User signed in.

 

 

 

 

and this one also

 

:06/27/2013 16:12:49.879:net.juniper.junos.pulse.android.ui.SignInActivity:a(-1): startSession: resumeSession=false host=y cookies=y
D:06/27/2013 16:12:50.78:android.net.http.SSLUtilities$MySSLSocketFactory:createSocket(-1): createSocket
D:06/27/2013 16:12:50.83:android.net.http.a:a(-1): Protecting SSL socket over Socket[address=/194.150.21.50,port=443,localPort=37721] 0
D:06/27/2013 16:12:50.88:android.net.http.SSLUtilities$MySSLSocketFactory:createSocket(-1): Protect socket 0
D:06/27/2013 16:12:51.431:android.net.http.SSLUtilities$MySSLSocketFactory:createSocket(-1): createSocket
D:06/27/2013 16:12:51.435:android.net.http.a:a(-1): Protecting SSL socket over Socket[address=/194.150.21.50,port=443,localPort=40904] 0
D:06/27/2013 16:12:51.437:android.net.http.SSLUtilities$MySSLSocketFactory:createSocket(-1): Protect socket 0
D:06/27/2013 16:12:52.617:android.net.http.SSLUtilities$MySSLSocketFactory:createSocket(-1): createSocket
D:06/27/2013 16:12:52.624:android.net.http.a:a(-1): Protecting SSL socket over Socket[address=/194.150.21.50,port=443,localPort=32926] 0
D:06/27/2013 16:12:52.626:android.net.http.SSLUtilities$MySSLSocketFactory:createSocket(-1): Protect socket 0
D:06/27/2013 16:12:53.913:net.juniper.junos.pulse.android.JunosApplication:k(-1): clearSession
D:06/27/2013 16:12:53.951:android.net.http.SSLUtilities:clearSessionCert(-1): clearing session cert
D:06/27/2013 16:12:53.972:net.juniper.junos.pulse.android.vpnservice.VpnService$2:cleanUpConn(-1): cleanUpConn called
D:06/27/2013 16:12:53.992:net.juniper.junos.pulse.android.vpnservice.VpnService$2:stopVpn(-1): stopVpn called maxMilliSecs=2000 m_threadRunning=0
D:06/27/2013 16:12:53.997:net.juniper.junos.pulse.android.ui.SignInActivity:a(-1): sessionSyncCompleted: errorCode=2
D:06/27/2013 16:12:54.165:net.juniper.junos.pulse.android.ui.VPNActivitySmiley SurprisednResume(-1): onResume currentSession = null
D:06/27/2013 16:12:54.609:net.juniper.junos.pulse.android.ui.SignInActivity:k(-1): Cannot unbind - HC service not bound
D:06/27/2013 16:12:54.648:net.juniper.junos.pulse.android.service.RemoteServiceSmiley SurprisednDestroy(-1): RemoteService onDestroy
D:06/27/2013 16:12:59.866:net.juniper.junos.pulse.android.ui.VPNActivitySmiley SurprisednPause(-1): onPause currentSession=null
D:06/27/2013 16:12:59.965:net.juniper.junos.pulse.android.service.RemoteServiceSmiley SurprisednCreate(-1): RemoteService onCreate
D:06/27/2013 16:12:59.972:net.juniper.junos.pulse.android.service.RemoteServiceSmiley SurprisednCreate(-1): vpnStateReceiver registered
D:06/27/2013 16:13:03.440:net.juniper.junos.pulse.android.ui.LogsActivity:a_(-1): JunosPulseActivityLog.txt

Visitor
Posts: 5
Registered: ‎09-09-2013
0 Kudos

Re: Android Support - devices cannot login after SA2000 upgrade to 7.1R15 and certificate change.

Guys,

 

I am having the same problem where I recently upgraded a stand alone SA2000 from 6.3 ->6.5->7.1R15 so that I could generate a 2048bit CSR. It was successful and the CA signed the cert and I installed it, great. Now only browsers and apple devices can login into the VPN. No andriod devices using Junos Pulse can login, also I am getting reports that Windows 8 clients also cannot connect but I am not seeing Windows 8 under supported systems for the 7.1 code.

 

I am able to reach the login page but when I enter the correct credentials, Andriod devices on Pulse saying: 'Failed to connect to server.' However I am seeing the user logged in under Active Users.

Moderator
Posts: 2,347
Registered: ‎11-19-2007
0 Kudos

Re: Android Support - devices cannot login after SA2000 upgrade to 7.1R15 and certificate change.

Yes, that is correct: Windows 8 is not supported with 7.1 (that support is introduced only with 7.3).

For your Android users, if you are seeing them logged in that means the authentication is succeeding (do you see the browser listed as Android/Pulse or desktop). The "failed to connect to server" message looks to be an issue with launching the VPN. Do you see any other messages after the successful login regarding the launch of the VPN (for example, no IP or DHCP pool)?
Visitor
Posts: 5
Registered: ‎09-09-2013
0 Kudos

Re: Android Support - devices cannot login after SA2000 upgrade to 7.1R15 and certificate change.

These are the only logs that show up.

 

Info

AUT22670

2013-09-09 11:31:22 - ive - [public ip] user ()[ Administrator Role] - Login succeeded for user/realm (session:00000000) from public ip.

Info

AUT24326

2013-09-09 11:31:21 - ive -[public ip] user ()[ Administrator Role] [] - Primary authentication successful for user/realm (session:00000000) from public ip.

 

 

The pulse client just say Failed to connect to server and thats it even though the SA2000 shows the user as logged in under active users.

 

 

 

 

     
     
New User
Posts: 1
Registered: ‎09-17-2013
0 Kudos

Re: Android Support - devices cannot login after SA2000 upgrade to 7.1R15 and certificate change.

Hi guys,

 

I've the same issue, after upgrade to 7.1r15

 

Info     AUT22670     2013-09-17 19:12:07 - ive - [IP PUB] Mxxxxx\pxxxx (User xxx pulse)[Users FULL pulse] - Login succeeded for Mxxxx\pxxxx/User XXx pulse (session:00000000) from IP PUB.
Info     AUT24326     2013-09-17 19:12:04 - ive - [IP PUB] Mxxxx\pxxxxx1(User xxx pulse)[] - Secondary authentication successful for Mxxxx\prxxxx/token from IP PUB
Info     AUT24326     2013-09-17 19:12:03 - ive - [IP PUB] Mxxxx\prxxxx(User xxx pulse)[] - Primary authentication successful for MIxxxx\prxxxx/Mixxx from IP PUB

 

all Android users reports  the "failed to connect to server" message!

 

with a 7.1R13 all works fine.

 

any ideas??

 

 

Visitor
Posts: 5
Registered: ‎09-09-2013
0 Kudos

Re: Android Support - devices cannot login after SA2000 upgrade to 7.1R15 and certificate change.

JUNIPER JTAC says that for 7.1R15, all andriod devices running Pulse 4.2.6.x will have problems to log in. Juniper is going to release a new version of Junos Pulse to fix this problem 4.2.7. It is due to be released in the first week of October. 

 

Sigma