dpalme
asked on
Accessing Exchange from remote
We are currently running exchange 2003 and have Outlook available via OWA and Citrix.
The problem is several of our salesman need to use it over a dialup connection, citrix seems to be running very slow on a dialup connection and it is getting frustrating with our sales staff.
We also need to keep the mail on the mail server, so I don't think running pop at this point is a viable option.
OWA is slower than Citrix is so that option sucks, not to mention that a user cannot compose messages offline with either of these methods.
Does anyone have a solution that will allow us to do the following:
1. continue to use Exchange 2003 (moving away from Exchange is ** NOT ** an option)
2. Allow users to work offline
3. Allow users to keep their mail on the server
4. provide a faster method (problem with speed has to do more with citrix taking so long to paint the damn screens, so when a user types a letter it doesn't take 5 seconds to display)
The problem is several of our salesman need to use it over a dialup connection, citrix seems to be running very slow on a dialup connection and it is getting frustrating with our sales staff.
We also need to keep the mail on the mail server, so I don't think running pop at this point is a viable option.
OWA is slower than Citrix is so that option sucks, not to mention that a user cannot compose messages offline with either of these methods.
Does anyone have a solution that will allow us to do the following:
1. continue to use Exchange 2003 (moving away from Exchange is ** NOT ** an option)
2. Allow users to work offline
3. Allow users to keep their mail on the server
4. provide a faster method (problem with speed has to do more with citrix taking so long to paint the damn screens, so when a user types a letter it doesn't take 5 seconds to display)
ASKER
Thanks for the article, I can see how the setup works, however on the CLIENT side when I go into the more settings and select "CONNECT USING INTERNET EXPLORER or 3RD PARTY DIALER, the modem drop down list stays greyed out. I cannot select "RPC..." from that list.
Any idea?
Any idea?
Are the clients Windows XP? Have you installed the hotfix for RPC support?
There is a very good white paper on setting up RPC over HTTP on Microsoft's web site.
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/ex2k3rpc.mspx
What about OWA? All you need to do is secure it with HTTPS, enable forms based authentication and punch 443 through your firewall to your Exchange server. It looks like Outlook 2003 so shouldn't be too difficult for your users to get to grips with.
Simon.
There is a very good white paper on setting up RPC over HTTP on Microsoft's web site.
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/ex2k3rpc.mspx
What about OWA? All you need to do is secure it with HTTPS, enable forms based authentication and punch 443 through your firewall to your Exchange server. It looks like Outlook 2003 so shouldn't be too difficult for your users to get to grips with.
Simon.
ASKER
OWA is ok, but over a dialup connection it is slower than citrix right now, I think part of the reason is it is sooooo heavy on graphics.
I noticed that the RPC over HTTP requires that the global catalog be sitting on a 2003 server and ours right now is on a 2000. Does anyone know if that will present a problem?
I noticed that the RPC over HTTP requires that the global catalog be sitting on a 2003 server and ours right now is on a 2000. Does anyone know if that will present a problem?
Try enabling forms based authentication for OWA (System Manager, protocols, http). This gives you the option of using the basic client which is faster over dial up.
You need to be at least mixed 2003 AD to use RPC over HTTP and point the registry changes at the 2003 DC.
This shouldn't be a problem - just DC Promo a Windows 2003 server up. The change isn't as great as going from NT4 to 2000.
Simon.
You need to be at least mixed 2003 AD to use RPC over HTTP and point the registry changes at the 2003 DC.
This shouldn't be a problem - just DC Promo a Windows 2003 server up. The change isn't as great as going from NT4 to 2000.
Simon.
ASKER
Sembee,
I'm not sure what your referring to when you say this gives you the option of using the basic client which is faster over dialup?
Basic client being what?
I'm not sure what your referring to when you say this gives you the option of using the basic client which is faster over dialup?
Basic client being what?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
See this
http://support.microsoft.com/?id=833401
Otherwise, we should be looking at why Citrix is so slow over dial-up. There will always be some performance degradation over dial-up, but it shouldn't be horrible. support.citrix.com You should be able to find lots of tweaks and reghacks to improve Citrix performance.