If it can help :
my particular situation (yesterday)
Ipad at home, view 5.2 is at work.
ipad is connected to work with native ipad Cisco IPSec VPN. (ESP)
Firewall/VPN at work lets tcp 443, tcp 4172, udp 4172 in.
No security server. Just connecting to internal CS. No tunneling. This is our temporary way in during view pilot.
The problem had been reported lately by some ipad users at work but iPads are not "production" yet for us and we do have a lot of other issues to work on.
Was trying to connect from ipad/home all day yesterday testing after 5.2 upgrade at work. Every other client combo possible worked. Even MAC view client 2.0 from home. Tera2 from work. Windows view client from work.
Ipad (using system status third party app) connection list indicated tcp 443 "close wait" (to connection server) and a tcp 4172 connection "syn sent" to the vm ... This means the first part (authentication by way of CS) seems to have gone well but that when the first phase of pcoip session started (tcp 4172) something was goin wrong along the way. Syn sent (along with op error message) is indicator Of problem
only when I read this thread and rebooted the ipad was I able to connect. This seems like a slam dunk ipad app or ipad problem. Can't tell what the trigger conditions are. Sorry.
I understand that problems can't be fixed if they are not reported but at the same time opening an SR requires commitment and time. As I said I have half a dozen already running and I am asked 2-3 times a day by vmware support to recreate problems and send logs ... This ipad one is not critical to me yet so i won't commit.