We use Juniper dynamic VPN with SRX320. I know that Pulse is developed by other company, but the VPN solution is anyway Juniper's so asking here:
In our case Pulse app shows totally mysterious Session time remaining times when we use SRX connection type. For example I have currently it 31646d 23h 14m... So till 3-Feb-2107. Would be nice if the connection would work that far but this doesn't sound very normal... Is this a bug in Pulse or Juniper that everyone has? Or what possible could cause this behaviour?
The time is actually roughly 2^32 max epoch time so calculation goes somewhere wrong if that should be supported.
Router time is right. Timezone is set. Ike and IPSec lifetime-seconds are correct ones.
We have had quite many connection issues that Pulse connects, but connection doesn't always work (perhaps 80% does). The problem occcurs with multiple Junos and Pulse versions. We are working on changing Juniper configuration to solve this. I just want to isolate that can this session time problem be related to our connectivity issues.