none
RPC over HTTP is very slow

    Question

  • I have published our OWA via ISA 2004 and configured RPC over HTTP. But it seems to be very slow. How can i improve better performance.

     

    If anybody know the solution please reply.

    Thursday, December 27, 2007 10:35 AM

All replies

  • Is outlook anywhere also slow when running on your LAN

     

    Thursday, December 27, 2007 5:59 PM
  • we are not using RPC over HTTP in our internal LAN network (For internal network we published via front end server), we are using RPC over HTTP only from outside. it seems to be slow and some times it says "Your Microsoft Exchange Server is Unavailable". Also i'm using a good ADSL line.

    Friday, December 28, 2007 3:35 AM
  • But if you configure to use RPC over HTTPS on the internal network, is it still slow?

     

    Friday, December 28, 2007 7:47 PM
  • Internally RPC over HTTPS is fast.

    Also for the external users, outlook web interface is fast.

     

    Internally also all out connections are HTTPS, and internal users are downloading mails from frontend server.

     

    Monday, December 31, 2007 5:03 AM
  • When is RPC/HTTPS slow? the logon process or all the time?

    are using ISA server with preauthentication or do just let SSL traffic through to RPCProxy?

     

    Monday, December 31, 2007 4:27 PM
  • When I open MS Outlook it is slow and if I press send/receive button also it is very slow. we are using SSL traffic through to RPC Proxy.

     

    Tuesday, January 01, 2008 5:51 AM
  • Is outlook running in cached mode? try to switch mode

     

    Tuesday, January 01, 2008 11:32 AM
  • Outlook is not running in cache mode.

     

    Wednesday, January 02, 2008 4:27 AM
  • have you tried to use outlook in cached mode?

     

    Wednesday, January 02, 2008 5:59 PM
  • Yes. i tried with cache mode also. that is also seems to be very slow.

    Thursday, January 03, 2008 5:28 AM
  • It seems that when using RPC over HTTPS, performance is slow regardless of traffic passes ISA. With that I take it that either your Front End server is overutilized or that something is configured incorrect on it.

    You are running RpcProcxy on your FrontEnd server?

    is the RpcProxy configured manually or do you let Exchange do it for you?

     

    Thursday, January 03, 2008 10:53 AM
  • front end server and RPC Proxy server is different. And the configuration is followed;

     

    front end server is the RPC over HTTP front end server and exchange server is the RPC over HTTP backend server.

    Monday, January 07, 2008 9:14 AM
  • Are you saying that the RPCproxy component is installed on your Exchange FE server or installed on another server?

    for easiest configuration it should be installed on your Exchange FE servers only.

     

    Monday, January 07, 2008 6:50 PM
  • Yeh, RPC component is installed in the FE server.

    Tuesday, January 08, 2008 2:35 AM
  • I'm having the same problems.  I tried changing the 401;x custom errors to "default" to see if that helps.  Please inform me if you've resolved this problem.

     

    Thursday, January 31, 2008 7:21 PM
  • I'm just now trying to resolve this for a client.  The server is SBS 2003 R1 with all the fun patches.  It's running with a GoDaddy SSL Cert, and everything works.  The client has people all over the country and some are complaining that by the time the client updates, they're off to the next meeting.  It works, it just needs to be faster.  The machine is a Dell / AMD server so we're not slacking on that side of the house.

    Is there a limit on the speed which I can adjust, either on the client or server side?  The server has a 100mbps internet connection  (in colocation) and has never used 1mbps.

    Thanks
    -Joe
    Monday, March 17, 2008 7:09 PM
  • I (a client user) am also experience the slowness over a newly created rpc over https connection with our office, but was trying to determine if it is just the norm for this type of connection or that I am truely slower than others. At first it took a few minutes to synch/create the folders which was expected.  However,  subsequent synchs takes 1 minute and 50 seconds to connect and synch the folders (without any new changes).  Is this normal or longer than it should be? 

     

    Thanks.

     

    Monday, April 14, 2008 1:55 AM