VPN
 

There's some discussion about VPN in the Pocket PC phone thread, but perhaps it's worth breaking it out here.

Anyway, what are people doing with VPN from mobile devices, especially Pocket PC type devices, to their corporate networks. I'm especially interested in working solutions (duh), but also interesting failures.
Thanks.
Rich

My company uses Cisco 3000's with the highest, most paranoid secure settings. http://www.flyertalk.com/travel/fttr...orum/smile.gif

I know that Cisco has come out with PDA clients, but my telecom group has only released Cisco's Wintel client to us (Cisco does not make their other clients generally available for download).

Having said that, I've been quite successful in connecting my laptop to my corp network through vpn using GPRS, T68, and its bluetooth link.

Actually most network related features in pocketpc's are pretty useless, even simple things like DHCP don't work reliably so I don't expect much luck getting a decent secure VPN working easier either...

The only reasonably safe way I access my office on my PocketPC is through Citrix but that requires a heck of a lot of scrolling...

I've heard of people getting VPN to work but haven't been successful myself. Have a Toshiba e740 otherwise connected successfully a Wifi router (can browse fine) but no luck with VPN. Also, the bundled VPN client on the PPC doesn't support IPsec (not my problem) although there are third party VPN clients out there.

Corporate e-mail in general is difficult to get remotely on a PPC. First, Pocket Outlook can only connect to a special mobile exchange server that your IT dept would have to install. If they don't want to do that, you'd be stuck with POP3 or IMAP access. Many companies only allow such access when you're connected to the network. Also, Outlook Web Access (OWA) is difficult to use. Pocket IE doesn't support OWA (b/c of Java issues or something). Doesn't seem like third party browsers do yet, although that may change. There are third party OWA server side solutions, but again you'd need your IT dept to support this. Some of this may be resolved with Exchange 2000, which my company is not using yet.