Re: Outlook Vs Outlook Anywhere

Thanks everyone.

Thats the kind of info I was after.

I can see Chris's point regards the bandwidth issues and also the name resolution issues.

We've many users who go overseas and hook up in hotels and then find that because the hotel LAN is on the same IP range as the office LAN they cannot resolve the Exchange server fqdn.

This would obviously get around this.

Looks like this is the way to go.

I've just stuck with running the CEICW to configure the server, seems the best way..

Next up is to try this on my SBS2008 test box.

Thanks guys.

Jim.

"blair003" <stepped@xxxxxxxxx> wrote in message news:120c4cbb-3915-4cd0-a294-961db3419c8b@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
PS: I didn't mean open port 80 - I am confused becuase of how it used
to be called rpc over http. but its actually over https as was pointed
out :)

On Mar 13, 10:38 am, blair003 <step...@xxxxxxxxx> wrote:
Outlook Anywhere (or just RPC over HTTP as it was called 2003) is just
another way of allowing remote users to connect to exchange using
outlook as though they were on the LAN.

IIRC, prior to SBS 2003, VPN used to be the only way to allow remote
users access to outlook. So a lot of places will still use this method
as that is how you had to do it in the past.

The advantages of outlook anywhere are arguably security and
simplicity. You open port 80 and 443, and that's it. Typically with a
VPN connection, the VPN clients are allowed access to a whole range of
ports -- the same ports they would have access to if they were
connected on the LAN.

If you need the VPN for other reasons, you might stick to connecting
to exchange over the VPN. If the VPN was only in place so that you
could connect with outlook to exchange, you would use RCP over HTTP.

Blair

On Mar 13, 8:22 am, "Jim" <j...@xxxxxxxxxxxxxxxxxxx> wrote:

> Have a SBS 2003 with 20 laptop users.

> In a nutshell what are the advantages or disadvantages of using an > Outlook
> Anywhere type connection as opposed to regular Outlook connected to > Exchange
> in the regular manner..

> One of the guys is telling me that where he used to work everyone was
> connected to Exchange without having to make a VPN connection like they
> currently do at this place.

> They share lots of items in each others mailboxes.

> Can this still be undertaken if they were setup with Outlook Anywhere ?

> Jim.

.

Relevant Pages

  • Re: RPC over HTTPS - Directory Connects TCP/IP Only (0/1)
    ... Connected-VPN.jpg is when I'm connected to the LAN via PPTP VPN. ... Outlook is fully functional. ... Disconnected.jpg is after the VPN connection closes. ... the Exchange server performing referrals first to itself, ...
    (microsoft.public.exchange.clients)
  • Re: OL2007B2 - Cannot Connect To Exchange Through VPN
    ... not sending any traffic to the exchange box other than the usual NETBIOS ... three VPN clients on two different laptops (Dell Latitude D600 and HP Compaq ... No activity across the tunnel from Outlook. ... VPN to an Exchange server on the same network as an Outlook 2007B2 client ...
    (microsoft.public.outlook.installation)
  • Re: Problem Connecting to Exchange Server from Outlook
    ... Teach Yourself Outlook 2003 in 24 Hours ... Outlook & Exchange Solutions Center: http://www.slipstick.com ... The connection to the Microsoft ... Exchange Server is unavailable. ...
    (microsoft.public.outlook)
  • Re: RPC over HTTP problem for some users only
    ... This will cause the Exchange ... The default connection methodology for Outlook 2003 when RPC/HTTP is ... Fast - TCP/IP then HTTP ...
    (microsoft.public.outlook.installation)
  • Re: Outlook 2003 over VPN to Exchange 2003
    ... Is the cycling between FQDN/NetBIOS on the DC/GC or Exchange server name. ... As for VPN connections all being the same.... ... If I ever needed to establish a connection that required Microsoft's IPSec ... earlier versions of Outlook don't know or can't do kerberos ...
    (microsoft.public.outlook.general)