Re: WM5, VPN via PPTP/MPPE, and direct connection to Exchange



Nik,

Sounds like we've resolved the MPPE then....

AKU is, for lack of a better description, the "build" your device is
running. On your device, go to Start>Settings>System>About and look at the
Build number. If you are running anything 14334.2 or later (higher number),
then you are running AKU 2.

AKU 2 allows for email and PIM data assuming your device is also a phone or
has WiFi functionality. This allows you to get your email and PIM data
"over the air" without needing to synchronize with your PC.

Before we get too far down this road, can you share what device you have?

Thanks,

--
Clinton Fitch, MVP-Mobile Devices
Clinton Fitch (Dot) Com!


"nik" <nik_AT_cict.co.uk> wrote in message
news:OSQB569vHHA.3508@xxxxxxxxxxxxxxxxxxxxxxx
Hi Clinton - thanks for the comments.

I've doone some research on this today and everything I'm finding points
to
the fact that MPPE doesn't work with Windows Mobile. I fully admit this
is
not an area I am strong in so I could be wrong - just basing it on an
hour
or so of research. There is a lot of information out there on this -
just
Live Search it.

That's what I found in practice - I just wanted to make sure I hadn't
missed
a config option.



As for direction connection to your Exchange server, it depends on what
you
mean. If you are using AKU 2

Sorry, you lost me there - what's AKU?

or higher you can configure your device to
synchronize all your PIM data and mail with your device so long as you
are
running Exchange 2003 SP2 or higher. Is that what you are needing to do?

Not sure what you mean by "configure your device to synchronise [data]
with
your device"..? I want to use the WM device as a standalone Outlook
client
for our Exchange Server, NOT synchronising with a client laptop.

All the walkthroughs I can see on Technet etc for WM devices seem to
assume
that the WM is used alongside a client PC, and synchronised with it - so
the
PC is used to install software, security certificates etc on the WM
device.
But we're trying to *replace* some of our current laptops with WM devices,
because laptops are an expensive option for users who don't need the
functionality of a full Windows / Office laptop. This means that our
scenario requires the WM devices to work entirely standalone, as Exchange
Server messaging clients.

Is WM a suitable option for this?

Thanks
nik


Thanks,


--
Clinton Fitch, MVP-Mobile Devices
Clinton Fitch (Dot) Com!


"nik" <nik_AT_cict.co.uk> wrote in message
news:%23P%23L9pwvHHA.784@xxxxxxxxxxxxxxxxxxxxxxx
Hello mobile people:

For years my company has been providing remote access to its SBS2003
network
(including Exchange Server) using a router-based VPN service - NOT a
public-facing Windows box running ISA Server. (The sysadmin likes to
keep
all his Windows boxes NATted. :-))

Standard Win2000/XP VPN clients connect to this VPN server without
problems - MPPE compression/encryption is automatically implemented by
the
VPN client over the PPTP connection, and the remote machines then have
LAN
addresses for accessing the Exchange Server.

Now I'm evaluating a Windows Mobile 5 device (Pocket PC type), and
trying
to
connect via the same VPN server - but the connection is dropped by the
server, I think because the VPN client in the mobile device doesn't
support
MPPE. Or at least because it doesn't automatically use it when
requested
on
a PPTP connection.

Is there any way of getting the VPN client in WM5 to use MPPE?

Also, is it possible to set up a WM5 device to communicate directly
with
Exchange? Part of the reason for evaluating these devices is to
replace
laptops, but all the walkthroughs I can find for deploying WM5 on
Windows
Server / Exchange (including cerificate installations) require that the
device is synced with a client PC. Is it practical to use WM5 devices
as
standalone clients on an SBS2003 system?

Thanks for any tips!

Nik








.



Relevant Pages

  • PPTP client not working on 4.10-R
    ... It needs to connect to a VPN server using PPTP. ... the client is running pptpclient-1.3.1. ... accept mschapv2 mppe ...
    (freebsd-questions)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • This is going straight to the pool room
    ... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
    (comp.os.vms)
  • [Full-Disclosure] R: Full-Disclosure Digest, Vol 3, Issue 42
    ... Full-Disclosure Digest, Vol 3, Issue 42 ... SD Server 4.0.70 Directory Traversal Bug ... Arkeia Network Backup Client Remote Access ...
    (Full-Disclosure)
  • Re: What doesnt lend itself to OO?
    ... > rather than client code. ... no way to do that without also touching the object with clock semantics ... will not encapsulate both clock semantics and network semantics. ... The server can do whatever it wants ...
    (comp.object)

Loading