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


Clinton already addressed the syncing issue, with a Windows Mobil 5 device
with MFSP installed you will be able to sync directly with the exchange
server. No VPN needed

Am I right that this strategy assumes a public-IP Exchange Server?
Currently we insist on a router-based VPN precisely because we're not keen
to give our Exchange Server a public IP - it's running SBS2003, and
therefore our entire company's IT core, so I do want to keep it behind a
hardware NAT and firewall.

Of course we could switch to using a public Exchange Server instead,
probably colocating in a datacentre somewhere - that's exactly the kind of
question I'm trying to answer with this evaluation.

Thanks
Nik

and if you use SSL (you really should) everything
will be secure between the device and exchange server.
--
--
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...

"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

  • RE: VPN Configuration error
    ... Remote Access wizard to configure VPN. ... How to move the client programs folder to another location in Windows Small ... or if the SBS SP1 did not finish the installation. ... On the SBS server, click Start, click Run, type "regedit" (without the ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN with SBS Premuim
    ... Windows 2003 SP2 networking issues, and then re-ran the CEICW again this time ... I understand that after installing ISA 2004 on the SBS ... server, VPN does not work. ... if you installed SP2 on the SBS server without ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Problem, PC not Authenticating with Server
    ... is the VPN server, SBS or router? ... Regarding the configuration of L2TP VPN, please also refer to the following ... 818043 L2TP/IPsec NAT-T update for Windows XP and Windows 2000 ... Computer certificates for L2TP/IPSec VPN connections ...
    (microsoft.public.windows.server.sbs)
  • RE: DST update for Exchange 2003 and Outlook 2003
    ... The Ldp GUI tool is included when you install Windows Server 2003 Support ... Microsoft CSS Online Newsgroup Support ... DST update for Exchange 2003 and Outlook 2003 ...
    (microsoft.public.exchange.admin)
  • RE: DST update for Exchange 2003 and Outlook 2003
    ... Majority of my users connect to Terminal Server and ... I also have users running on stand-alone PC's (Windows XP) ... run the Outlook Time Zone Data Update Tool or the Exchange calendar tool? ... 926666 Update for daylight saving time changes in 2007 for Exchange 2003 ...
    (microsoft.public.exchange.admin)
Loading