This content has been marked as final. Show 3 replies
the problem I think is that the Cisco VPN does not expect to be 2nd in line - we shim the gina chain so we can do the automatic login for the user, but some gina writers never consider that situation.
I expect you'll find that with all the EEPC windows login options off, it works fine, but when on, Cisco gets upset. The only difference between the two is the gina order.
This is not something we can fix unfortunately - Cisco needs to change things so their gina is happy to be later on, or you need to set something in that gina to make it happy.
Check out this post:
A few of the gurus go over a few troubleshooting steps in reordering the GINAs as well as disabling some unneeded devices.
Thanks for the advise, I was hoping for a way to prevent this occuring in the first place.
Guess we'll have to muddle on fixing the problems as they occur. When we finish our rollout we should no longer have these issues.