Cisco Anyconnect and iPads
Iristheangel
Mod Posts: 4,133 Mod
in Off-Topic
Hello all,
I'm wondering if anyone else has seen or resolved this issue. I've been crawling around on the Apple and Cisco forums and opened a Cisco TAC case without much help. No one can seem to figure out why this is happening.
So my company wants to buy iPad minis for some of the executives to VPN in and use Jabber with. We've never really used iPad for anything like that before so it's all sort of new for us. Last week it was brought to my attention that Cisco Anyconnect would disconnect upon iPads going onto standby and not try to reconnect upon waking the device. I thought that was a little strange so after some modification, I created a profile on the ASA 5520 (Version 8.4(3)) that would allow reconnect upon device wake. Now, this solved the problem for all devices AND iPads on WiFi, but the iPads that are connecting via 4G/3G are still having the same issue. When I leave them alone for about 5-10 minutes and come back, it'll still show the VPN as being connected but when I try to ping an internal server, it'll timeout. This issue doesn't seem to happen with Android devices and with WiFi iPads so that makes it a little strange. I opened a Cisco TAC case but the engineer I got had NO idea why this was happening and I'm sitting here in my PJs waiting for this to be escalated to another engineer.
Anyone else have this issue? Any resolution or did you just decide to play with Androids instead?
I'm wondering if anyone else has seen or resolved this issue. I've been crawling around on the Apple and Cisco forums and opened a Cisco TAC case without much help. No one can seem to figure out why this is happening.
So my company wants to buy iPad minis for some of the executives to VPN in and use Jabber with. We've never really used iPad for anything like that before so it's all sort of new for us. Last week it was brought to my attention that Cisco Anyconnect would disconnect upon iPads going onto standby and not try to reconnect upon waking the device. I thought that was a little strange so after some modification, I created a profile on the ASA 5520 (Version 8.4(3)) that would allow reconnect upon device wake. Now, this solved the problem for all devices AND iPads on WiFi, but the iPads that are connecting via 4G/3G are still having the same issue. When I leave them alone for about 5-10 minutes and come back, it'll still show the VPN as being connected but when I try to ping an internal server, it'll timeout. This issue doesn't seem to happen with Android devices and with WiFi iPads so that makes it a little strange. I opened a Cisco TAC case but the engineer I got had NO idea why this was happening and I'm sitting here in my PJs waiting for this to be escalated to another engineer.
Anyone else have this issue? Any resolution or did you just decide to play with Androids instead?
Comments
-
inscom.brigade Member Posts: 400 ■■■□□□□□□□I am sure that I am far from being on target, since BYOD, jabber have new and evolving tecnology issues, I haven't worked with Jabber, this is the second time I looked at it.
you have probably been at this link.
Before you begin* [Cisco Jabber for iPad] - Cisco Systems
Cisco ASA 5500 Series Configuration Guide using the CLI, 8.2 - Configuring Connection Limits and Timeouts* [Cisco ASA 5500 Series Adaptive Security Appliances] - Cisco Systems
Rackspace, or Amazon must have solved this already. -
Iristheangel Mod Posts: 4,133 ModSadly, I made all those adjustments and nothing worked but the problem actually fixed itself today. Cisco released a new Anyconnect version for the iPad and it fixed the timeout issue magically.
-
NotHackingYou Member Posts: 1,460 ■■■■■■■■□□Try this: pearworks: software scroll down to pearportVPN.
Edit: Oops, looks like they don't have an iOS version. Maybe you can find something similair?When you go the extra mile, there's no traffic. -
J_86 Member Posts: 262 ■■□□□□□□□□Iristheangel wrote: »Sadly, I made all those adjustments and nothing worked but the problem actually fixed itself today. Cisco released a new Anyconnect version for the iPad and it fixed the timeout issue magically.
Don't you love when stuff "magically" gets fixed?