4.4.03034 - Cascading Error Messages

[John Getzke]

Hello,

We recently deployed Secure Mobility Client 4.4.03034 and received a screenshot back from a user who captured a cascading error message on the desktop.

Normally I would expect the VPN to continue retrying to connect due to our policy but reuse the same error box each time.  In this scenario it seems that the VPN client misfired and launched a new error message for each attempt.  The machine was left online overnight to a cellular connection.  The machines cellular connection remained connected to the network but the internet appears to have been dropped behind it.  A reboot brought the machine back online with no problem once the user woke up and noticed what was going on.

Is this something that is patched in the most recent 4.4 client?

Attached is a screenshot of the cascading error.

[Mohammad Alhyari]

Hi,

1- How many users are seeing this problem?

2- is it easily reproducible?

3- does it happen with one version only?

would it be possible to try the latest one here?

https://software.cisco.com/download/release.html?mdfid=286281283&flowid=72322&softwareid=282364313&release=4.5.01044&relind=AVAILABLE&rellifecycle=&reltype=latest

[John Getzke]

1. Only one user so far.  We recently completed a deployment of 4.4.03034 last week so we may get more.  Leaving the cellular connection online overnight is not likely to be a unique scenario.

2. Maybe.  The theory is if we leave a cellular connection online overnight that Verizon will disconnect the internet access to that session at some point.  The machine would still have a Verizon IP address and our policy will continue to trigger reconnections and failures until the user intervenes.  Going to try and confirm this theory next.

3. Yes, this is a new problem for us with this specific Cisco VPN client.

>would it be possible to try the latest one here?

We have code for the latest 4.5 client and are actively testing this version for another fix we were waiting on.  Hopefully this problem is isolated to the 4.4 client.  If we can recreate the scenario and 4.5 resolves it then that is an acceptable solution.

[Mohammad Alhyari]

If it is reproducible and not fixed with 4.5 would it be okay for you to log a case with TAC regarding this?

if yes please ping me with the case number once you do that.

Moh,

[John Getzke]

Will do.

[John Getzke · Accepted solution]

We have not been able to reproduce this problem and are soon moving to upgrade everyone to 4.5.  No other cases have been reported so we can safely dismiss this as a temporary problem for now. 

Thanks for the responses though.