VPN Woes on Imate PDA2K

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Aresflight (jmh1961_at_swbell.net)
Date: 10/20/04 

Date: Tue, 19 Oct 2004 21:32:51 -0500

I'm struggling... here's my situation.

I just bought one of the imate PDA2K models from Expansys (also known as MDA
III in some circles).

I have Tmobile GPRS VPN service (internet3.voicestream.com), which I have
used with both an XDA I and an Mpx200 smartphone to VPN into my work
Exchange mail via a PPTP server.

This imate unit comes with Windows Mobile 2003 SE - ROM version 1.12.00 WWE
(which I believe means 'world wide english' version).

I am able to establish a good GPRS connection under "My ISP" in Connection
Manager. I can surf the web just fine.

I set up "My Work Network" as I have before on XDA I and my Mpx200 (both of
which worked) to my PPTP server - nothing special about the settings I'm
using. The Modem tab is left blank, as is the Proxy Settings tab. VPN type
is PPTP. Other 'Advanced' settings are typical:

Use server assigned IP address is selected.
Use software compression is selected.
Use IP header compression is selected.

There is a separate applet on this unit labeled "GPRS Setting" which has two
tabs. The first selects between PAP and CHAP authentication. PAP is selected
as the default. The second selects between class 8 (4R1T) and class 10
(3R2T). Class 10 is selected as the default. Not clear to me if these
settings matter for my situation.

I set up my Inbox POP3 account to my Exchange server as I always have
(again, it worked on the other two devices with exactly the same settings -
no differences).

When I try to connect to access my mail, the GPRS connections is made,
followed by the VPN connection... all looks like it works, VPN connection
starts a clock in the bubble popup on the screen. But Inbox just sits there.

Another annoyance (could have sworn that I was able to do this on my XDA I)
is that when I connect my VPN connection manually and try to surf to some
work-related intranet websites, the device automatically deselects VPN and
defaults to just the GPRS connection.

Have read things about 'certificates' and such, which I can't tell whether
they do or don't matter.

I have a limited window here where I can still return the device for a
refund if it won't work. Any advice on what I can do or where I might go for
help?

Note: I have also tried the connection via WiFi connection to the Internet
via my Wireless router, same deal... I can surf the web just fine on WiFi
but when I connect to my VPN server it just sits there when I try to surf to
an intranet site or download mail from Exchange (Inbox just says
'Connecting...', never gets around to 'Logging in...'

Relevant Pages

  • RE: VPN issue on SBS2003
    ... I understand that you encountered VPN connection issue when you use VPN to ... Internet clients or VPN to external VPN Server from SBS Client computers? ... Configure E-mail and Internet Connection Wizard ... Total GRE packets sent = 1 ...
    (microsoft.public.windows.server.sbs)
  • RE: PPTP VPN connection problems
    ... The problem is that the VPN does not disconnect. ... However after some idle period I can not send packets across the connection. ... A ping to the server would result in "Request timed out". ... If I connect with the VPN client locally to the internet ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN Ports to Open
    ... the VPN connection after you change the firewall before SBS. ... On the server, please stop the Routing and Remote Access service. ... Total GRE packets sent = 1 ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2003 VPN Default Gateway Issues
    ... Ethernet adapter Local Area Connection: ... If the VPN server is configured to use a static IP address ... the default gateway on the client is not the problem. ...
    (microsoft.public.windows.server.networking)
  • RE: VPN Connectivity issues through LAN
    ... I understand that you cannot ping SBS after ... you can establish VPN connection from the remote LAN. ... You have to rerun the CEICW to make sure your SBS 2003 server have right ...
    (microsoft.public.windows.server.sbs)