OWA 2003 vs Outlook 2003/Outlook 2003 RPC/HTTP

Exchange 2000


  • 1. Outlook 2003 and Exchange 2000 or Exchange 5.5
    Will the new clients work with the old Exchange servers?
  • 2. OWA 2K3 vs Outlook
    Are there more features in OWA than any Outlook client? Thank you, Jim
  • 3. OWA Error, Exchange 5.5
    I've got one user getting "Failed to Connect to Exchange Server, <servername>" when he tries to login to OWA. OWA is working fine for other users, and he is the only one with the error. I found a couple of articles about this error and have tried each (working on mapisvc.inf) to no avail. I have also checked his permissions on the mailbox and his account is configured just like mine, but mine works. Any other ideas? Thanks! Chris
  • 4. Admin access to others accounts
    I'm running Exchange 2000 & Outlook 2002. I'm the administrator. How do I grant permission to open other exchange accounts from my system? I go in an add the other mailbox to my Exchange profile but I don't have permissions. Like I said I'm the Admin and my user is in the group Domain Admin but I still can't. What do I need to do?

OWA 2003 vs Outlook 2003/Outlook 2003 RPC/HTTP

Postby Jesus Martin » Sat, 10 Mar 2007 02:28:47 GMT

Hi all,

I would like to get your feedback regarding a customer scenario. Customer 
has 2 sites, 1 with 1000 users and 1 with 500, Sites are connected thru 4x2 
Mbps lines

They want to deploy an Exchange 2003 cluster in the biggest site and they 
would like to avoid the need of deploying aditional mailbox servers in the 
second site and the question is what the recommended client in this scenario 

They want to deploy a FE/BE topology with a FE in the second site. they have 
DCs and GCs in the second site, and they are asking what client will provide 
the end users the best performance.

I have been reading many documents and seems Outlook 2003 with Cache mode is 
the best option (here they would not install the FE), then Outlook 2003 
RPC/HTTP as the second one and finally OWA

From your experiences what is the best client we can deploy in this 
centralised topology, giving the end users the best performance?


RE: OWA 2003 vs Outlook 2003/Outlook 2003 RPC/HTTP

Postby SmFjaw » Sat, 10 Mar 2007 23:56:10 GMT

Outlook with RPC in cache mode is by far the option with the least bandwith 
all other options consume between 30% and 300% more.
(worst case is owa without compression)


Similar Threads:

1.Outlook 2003 vs Outlook 2003 RPC/HTTP

Hi all,

would like to confirm what the best option is, company has 2 sites, all the 
Exchange servers are in Site 1 and 500 users from site 2 will connect to 
those servers, communication between sites is ok (around) 8 Mbps, my 
question is, would make sense to deploy a front end in site 2 and make the 
users RPC/HTTP enabled? or MAPI with cache opcion enabled?

mailbox server is 2 CPUs and 4 Gbs of memory serving 1500 users.

i am a little concern in the way that the exchange servers at site 1 will 
support all the MAPI connections thats why we are thinking that adding a FE 
in the second site may reduce the overload in the exchange central servers


2.Outlook 2k3 vs Hosted Exchange 2003 RPC over Http login problem

Is, it in any way, possible to autologin to this kind of exchange.
Everytime, i restart Outlook i gives me a login promt.

Could this be controlled byg regedit or something similar ?


3.Outlook 2003 on Windows 2003: RPC over HTTP?

We deployed Exchange 2003 based on Windows 2003 AD. Our Windows XP user can 
access Exchange Server by using RPC over HTTP without any problem.

We have Windows 2003 on which we installed Outlook 
2003 with SP1. Our users will use RPC over HTTP from this client also. 
Unfortunately they cannot connect from this computer to Exchnage by using RPC 
over HTTP. They have no problem with OWA connections.

Is there any restrictions if a Windows 2003 Server is deployed as Outlook 
2003 client?  Can we use Outlook 2003 on Windows 2003 Server for RPC over 
connections? How can we fix this problem?

Best Regards

4.Outlook 2003 RPC over HTTP to Exchange 2003

5.Exchange 2003, Outlook 2003, and RPC-HTTP

I've been working my way through setting up a RPC-HTTP connection between 
Outlook 2003 and Exchange 2003.  It's to the point that an internal (within 
the local network and domain) RPC-HTTP connection seems to work fine.  Also, 
I've used IE to connect to Exchange's RPC folder (example - 
https://mail.exchangeserver.com/rpc and then filled out a challenge box for 
user name and password).  The proper error page shows up (403.2 Forbidden: 
Read access is denied) and everything seems fine.
But Outlook can't find the server.  I've made repeated attempts to connect 
with Outlook in rpc diagnostic mode (DOS box - "outlook /rpcdiag") and get 
the challenge box for user name and pass; but it never finds an Exchange 
server.  I've tried to put the user name in different formats: 
domain_name\user_name, server_name\user_name, just user_name, and so on; just 
to see if it mattered.
There is a PIX 501 firewall sitting between external clients and the 
Exchange server.  The PIX is setup to allow/pass traffic from ports 80 (HTTP) 
and 443(HTTPS) to the Exchange server.  Since the RPC packets are being moved 
via HTTP, I have not punch a hole for RPC in the firewall.
The Exchange I'm using is part of the Small Business Server 2003 package.  
SBS made it easy to setup the Exchange side of RPC-HTTP (a wizard and a check 
box later it was ready) and I've gone through different 'How to' FAQs that 
verified Exchange's setting are correct.  So I'm left with the firewall 
and/or the client.

Any help on this would be great.


6. RPC Over HTTP Problems Exchange 2003 and Outlook 2003

7. Configuring Exchange 2003 & Outlook 2003 for RPC over HTTP

8. Outlook 2003 HTTP/RPC to Exchange 2003 problems

Return to Exchange 2000


Who is online

Users browsing this forum: No registered users and 10 guest