Hi there,

I am a frustrated would-be user of Windows Mobile devices. The problem
lies in the fact that no matter the device, OS version, or carrier that
I try (even Wi-Fi) - I cannot get a Windows Mobile device to connect to
my company's PPTP VPN server. Or rather, they all show that the
connection is made, but is immediately dropped after I try to connect
to any internal web pages or use ActiveSync, etc.

(FYI - I've tried connecting to my company's PPTP VPN using Macintosh
OS X, Windows Vista, Windows XP, and an iPhone: all of them work great
- only the Windows PocketPC / Mobile devices have issues).

So, here is what I've tried so far:

On AT&T (with various SIM card including that of a store manager):
1. The new Tilt (HTC TYTN II, a.k.a. 8925, a.k.a. Kaiser) - WM6
2. Siemens SX 66 - PPC2003

On Sprint:
1. Mogul.

On T-Mobile:
1. Wing

On every device, I was able to browse the Internet and set up the PPTP
VPN. However, once the VPN was connected (at least according to the
device), the connection was dropped as soon as I tried to go to a
company Intranet page.

Finally, I have spoken with my corporate IT dept. and they've said that
the VPN is a MSFT 2003 PPTP VPN using MSCHAPv2 authentication, in
strict mode (requiring all routing through that VPN for all traffic).

Any thoughts? OR do Windows Mobile devices just not work with PPTP VPNs?

Thanks,
Eric

You need to add any dotted addresses to the device excpetions list. If you
don't the connection manager will drop the tunnel thinking that you wanted
to be on the internet. PPTP & L2TP for that matter works very well in
Windows Mobile, getting the initial connection to launch is a pain but the
connection is solid. The exceptions list can be found by tapping
Start>Settings> Connections(tab)>Connections(icon)>Advanced(tab)>E xceptions.
If your company uses computer.suffix you can enter and exceptions like this
(*.domain.whatever), if you're using just IP's then just enter those in.

--
--
Eric Hicks [That_Kid] (MS-MVP Mobile Devices)

The MS-MVP Program - http://mvp.support. microsoft.com This posting is
provided "AS IS" with no warranties, and confers no rights...

"Eric Flyermusician" <eflyermusician********.com> wrote in message
news:2007101118430116807-eflyermusician********com...
> Hi there,
>
> I am a frustrated would-be user of Windows Mobile devices. The problem
> lies in the fact that no matter the device, OS version, or carrier that I
> try (even Wi-Fi) - I cannot get a Windows Mobile device to connect to my
> company's PPTP VPN server. Or rather, they all show that the connection
> is made, but is immediately dropped after I try to connect to any internal
> web pages or use ActiveSync, etc.
>
> (FYI - I've tried connecting to my company's PPTP VPN using Macintosh OS
> X, Windows Vista, Windows XP, and an iPhone: all of them work great -
> only the Windows PocketPC / Mobile devices have issues).
>
> So, here is what I've tried so far:
>
> On AT&T (with various SIM card including that of a store manager):
> 1. The new Tilt (HTC TYTN II, a.k.a. 8925, a.k.a. Kaiser) - WM6
> 2. Siemens SX 66 - PPC2003
>
> On Sprint:
> 1. Mogul.
>
> On T-Mobile:
> 1. Wing
>
> On every device, I was able to browse the Internet and set up the PPTP
> VPN. However, once the VPN was connected (at least according to the
> device), the connection was dropped as soon as I tried to go to a company
> Intranet page.
>
> Finally, I have spoken with my corporate IT dept. and they've said that
> the VPN is a MSFT 2003 PPTP VPN using MSCHAPv2 authentication, in strict
> mode (requiring all routing through that VPN for all traffic).
>
> Any thoughts? OR do Windows Mobile devices just not work with PPTP VPNs?
>
> Thanks,
> Eric
>

Hi Eric,

Yeah, I've tried that as well. I've also tried putting in "*/*", which
I've been told routes al Internet traffic through my company's VPN. It
still didn't work.

Best Regards,
Eric

On 2007-10-13 17:12:59 -0700, "Eric Hicks [MVP]" <i'm@home.with.u> said:

> You need to add any dotted addresses to the device excpetions list. If
> you don't the connection manager will drop the tunnel thinking that you
> wanted to be on the internet. PPTP & L2TP for that matter works very
> well in Windows Mobile, getting the initial connection to launch is a
> pain but the connection is solid. The exceptions list can be found by
> tapping Start>Settings>
> Connections(tab)>Connections(icon)>Advanced(tab)>E xceptions. If your
> company uses computer.suffix you can enter and exceptions like this
> (*.domain.whatever), if you're using just IP's then just enter those in.
>
> --

Actually that should be *.*
What happens if you use the netbios name of a machine? Also download VxUtil
from www.cam.com and when you establish a vpn connection try to ping
something on the other side of the tunnel from your device.

--
--
Eric Hicks [That_Kid] (MS-MVP Mobile Devices)

The MS-MVP Program - http://mvp.support. microsoft.com This posting is
provided "AS IS" with no warranties, and confers no rights...

"Eric Flyermusician" <eflyermusician********.com> wrote in message
news:2007101409043016807-eflyermusician********com...
> Hi Eric,
>
> Yeah, I've tried that as well. I've also tried putting in "*/*", which
> I've been told routes al Internet traffic through my company's VPN. It
> still didn't work.
>
> Best Regards,
> Eric
>
> On 2007-10-13 17:12:59 -0700, "Eric Hicks [MVP]" <i'm@home.with.u> said:
>
>> You need to add any dotted addresses to the device excpetions list. If
>> you don't the connection manager will drop the tunnel thinking that you
>> wanted to be on the internet. PPTP & L2TP for that matter works very
>> well in Windows Mobile, getting the initial connection to launch is a
>> pain but the connection is solid. The exceptions list can be found by
>> tapping Start>Settings>
>> Connections(tab)>Connections(icon)>Advanced(tab)>E xceptions. If your
>> company uses computer.suffix you can enter and exceptions like this
>> (*.domain.whatever), if you're using just IP's then just enter those in.
>>
>> --
>
>