Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1039
  • Last Modified:

Exchange 2010 and 2003 ActiveSync and RPC over HTTP Coexistence

Hello,
     I am almost done with my Exchange migration, but I have run into a snag. First, let me give a background on the current setup. We have an Exchange 2003 server and an Exchange 2010 server in coexistence, and email filtering from MXLogic. I can access both servers without issue from inside the network. However, since we only have one static IP, the mailboxes on the Exchange 2010 server cannot be accessed from the outside, that is, with ActveSync, OWA, or RPC over HTTP. I guess this is likely because the router/firewall is configured to pass exchange traffic to the 2003 server. What I'd like to be able to do is use both servers from the outside if possible. Is there a way to make the traffic flow to the exchange 2010 server from MXLogic, and then make the Exchange 2003 server a kind of backend server? Although, the mailboxes on 2003 should still be accessible via ActiveSync and RPC over HTTP. Thanks!
0
indigo6
Asked:
indigo6
  • 4
  • 3
1 Solution
 
Julian123Commented:
Yes, you can do this. When I set up Exchange with 2003, I configure the firewall to direct all incoming SMTP (port 25) and ActiveSync/RPCHTTP (443) to Exchange 2010. Exchange 2010 will pass any incoming SMTP email to Exchange 2003 as needed. For ActiveSync and RPC/HTTP, it will also proxy those connections to Exchange 2003.

Please note that this will not work for Outlook Web App, as making network requires having a separate, publicly accessible, URL and IP for Exchnage 2003.
0
 
Julian123Commented:
As some additional background, here is an article describing how proxying works: http://www.exchangebytes.com/?p=598

And one other from Microsoft: http://blogs.technet.com/b/exchange/archive/2009/12/08/3408985.aspx
0
 
indigo6Author Commented:
Ok, nobody uses OWA on 2003 anyway, so that's good. So no configuration necessary on the exchange servers? All I need to do is configure the firewall?

I noticed that when I created a test account on the 2003 server and tried to connect to it via the 2010 server it failed to verify. (Testing from iOS)
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Julian123Commented:
There is a step you need to take on Exchange 2010, specifically setting the appropriate authentication mechanism on Exchange 2003.

Please take a look at this page: http://technet.microsoft.com/en-us/library/ee332348(v=exchg.141).aspx. Under the heading "installing exchange 2010, take a look at step seven.

In general, though, I do recommend looking through the whole page just to see if you've done all the steps it recommends.
0
 
indigo6Author Commented:
Ok, I did all the steps. Thanks! Is there a way I can test the proxying before going live on the router?
0
 
indigo6Author Commented:
I had to do one more step, specifically disabling the SSL requirement on the Microsoft-Server-ActiveSync vdir on the Exchange 2003 server, and it worked.

I'm setting the router to use the Exchange 2010 server this weekend. Is there any way to test first? Thanks!
0
 
indigo6Author Commented:
In this case, since we had a single server combination front end / back end Exchange 2003 server, it took several things to get Exchange 2010 to proxy Exchange 2003:

1. Enable Windows Integrated Authentication on the Exchange Active Sync Virtual directory on the Exchange 2003 server using the Exchange System Manager. (Install this hotfix if necessary: http://support.microsoft.com/?kbid=937031)
2. Disable Forms based authentication on the Default Web Site on the Exchange 2003 server. I did not have to reset the Directories though. A simple restart, or restart of the IIS services did it.
3. Disable the SSL requirement on the Exchange, and Exchange Active Sync virtual directories. (Since the Exchange 2003 server no longer faces the Internet) Again, restart the services, or reboot the server.

This was mainly for ActiveSync, but RPC over HTTP (Outlook anywhere) worked fine as well.

Thanks!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now