• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 205
  • Last Modified:

Exchange 2003 Main Site, Exchange 2010 Remote sites

I have an issue where we have installed our second exchange 2010 server. Both 2010 servers are on remote sites and can't directly communicate. We have an exchange 2003 server on our main site which the remote sites have a VPN back to.

Since installing the second exchange 2010 server, I have a large number of emails queued up at each 2010 site. I have routing groups between the exchange 2003 and 2010 sites in place.

Antoher strange issue is that from the new 2010 site, I can't email to users on the 2003 site. It tries to send through the other 2010 site (which it can't connect to)

Any help would be appreciated as I'm currenlty onsite but only for another 12 hours
0
coreit
Asked:
coreit
  • 2
  • 2
1 Solution
 
AkhaterCommented:
wow that's quite an unusual setup I am not sure it can be solved but I willing to give it a try.

first thing to do is to create another routing group connector between your new 2010 and the 2003

run

New-RoutingGroupConnector -Name "Anything" -SourceTransportServers "new2010.domain.com" -TargetTransportServers "2003.domain.com" -Cost 1 -Bidirectional $true

this should get the traffic between the new 2010 and the 2003 working (After replication occurs)

also check if it fixes all your routing issues, if not let me know
0
 
coreitAuthor Commented:
Tell me about it!

So I have an update and a solution.

Firstly, I had the routing groups between the 2010 and 2003 in place just as you had suggested. I even removed them and re added them.... but it didn't resolve my issue.

So, after way too many hours of researching, at 5am I decided to install a 2010 hub transport server in my existing 2003 site. As soon as the installation completed and a site replication took place, all 100+ pending emails were sent to their required server!

Learn Learnt: You must have a 2010 exchange hub transport service in the middle of your 2010 servers. You can't have a 2003 server sitting in the middle.

Let me clear up my original issue
1. I have a hub-spoke network config
2. my remote sites can't see each other

Everything is now working with that one further installation.

Thanks Akhater for repliying to my question (it was my first question after many years of experts-exchange memebership- I will be sure to ask again in the future now that I know how quick people respond)

Cheers
0
 
coreitAuthor Commented:
The installation of a central 2010 hub transport service fixed the issue immediately. See my post for further explaination.
0
 
AkhaterCommented:
yea a hub in the 2003 site will surely solve things up, just consider to delete the existing routing group between 2003 and 2010 in the remote site and replace it with a connector between 2003 2010 in the same site
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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